Automated web application testing is easy, right? You sit down at a client computer, pop open a browser, record a few scripts that reflect test cases, then set them up to execute automatically on the application. You may have to go in and adjust some of the parameters to make sure the script with exercise the right control with appropriate data, but other than that, you’re ready to play back those scripts during normal testing activities. But one wrinkle is that actual use is a little messier than that. For example, users are likely to use different browsers with your ...
August 01, 2013