itesting wrote:How would you apply eValid to testing of mobile applications?
The basic approach we take to testing a mobile application is the same as for any application: We use eValid, after appropriately configuring it to present the right kind of "face" to the server, to verify and validate the functional behavior of the application.
In case you are using an IE browser, in which case eValid defaults to imitating the IE browser, then what you see on the screen is what an IE user sees. But, what is visible on the screen is NOT usually where performance and content issues lie -- and are detected. What's visible is a "rendering" of the data that is deliver over the HTTP/S wire to the browser, but in most cases that information is not crucial in terms of page performance or server capacity checking.
So, when you are testing an application for response in a mobile application all of the usual eVald validation and verification tests, and performance and timing tests as well, operate as you would expect.
The eValid Support Team
by itesting » Tue Apr 19, 2011 9:42 am