When developing a web application, several versions of the application may exist on different servers for testing purposes before the application is published to the live site. A developer may use a web server on their own machine to test a site while they are developing it. Alpha or beta versions of the web application may be put on a staging server so the QA group can test it. Finally, the application will be published to a live site. In QA Wizard Pro, it’s easy to use a single script to run an automated test against the web application in each configuration.
First, create a new web application and enter the path to your web site in the URL field. Make sure the Create repository variable option is selected. You may need to edit the text shown in the %URLROOT% field to include path information to your application.
In this example, you can see that I’m using my local machine, “petev960.seapine.com”, as my test web site and I have the WysiCorp test application in a subdirectory of the same name. Because the entire web application is in this directory (and on a real server it may exist in some other directory) I’ve included the “wysicorp” part of the path in the %URLROOT% field.
I can then record and play back scripts against my test application without worrying about the %URLROOT% variable. QA Wizard Pro will detect when my web site pages, links, and images start with this URL root and replace it with the variable as appropriate.
When I’m ready to test this web application on a different site, I can open the Version properties dialog (by expanding the “WysiCorp” application, right-clicking on the “1.0″ version, and selecting Properties). To view the information stored about the %URLROOT% variable, I click the Repository Variables tab. Since I want to be prompted for the site to test against when running a script, I select the checkbox in the Prompt column. To add a new site, I click on the + button that appears in the item under the Default Value column (select the item in the column to see it).
Clicking the button opens a list editor dialog box that lets me add other sites that I may want to test this same set of scripts against. I add “http://www.seapine.com/wysicorp” to the list as the live version of the WysiCorp web application.
When I’m done, I click OK to return to the repository variables list and OK again to return to QA Wizard Pro.
Now, when I play back the script, I am presented with a choice of web sites to test against.
I can select the new site, “http://www.seapine.com/wysicorp”, and see that QA Wizard Pro is then able to test the published site without any script modifications.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
Related posts:
