While a QA Wizard Pro load test is running, a great deal of activity is occurring on your web server. You can use built-in performance tools on the web server to better pinpoint the type of stress that load testing is causing your server. This information allows you to better identify which pieces of your web application may be causing your server the most pain.
Watch the following video to see how to create and correlate this data.
When load testing against a web application, you may want to create a set of scripts that simulates what activities most users perform. After using your web metrics to determine where users spend their time, you can create a script for each common user action. Using the QA Wizard Pro Load Testing options, you can then match up how often your scripts are run as compared to how many users actually perform those actions.
Watch the following video to see details on how to set this up.
Virtual machines offer a great way to run automated scripts in a separate, customized environment of your choosing. The virtual environment can exist without interfering with your normal computer. You can configure the virtual machine to ensure the environment remains constant on each script run. One way to make better use of actual machine resources is to have QA Wizard Pro start up and shut down the virtual machine on its own. This way the machine is only running when it is being used for automation.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponGeneric controls are those controls that an automated testing tool doesn’t natively recognize. They may show up with actions like LMouseClick or MouseMove on them along with the coordinates that the mouse action occurred at. These aren’t very useful when testing, as their available actions are limited and you might have to go through some extra work if you want to checkpoint data on them. QA Wizard Pro 2010 introduced a feature to change all of that.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponWhen 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.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponKeyword-driven testing is a testing methodology that allows you to separate the actions that you want to perform from the automated script that executes the given actions. The actions can be entered into a table, such as an Excel spreadsheet, and then run by an automated script. Since the QA Wizard Pro scripting language mirrors these keywords in its own implementation, keyword-driven testing with QA Wizard Pro is easy.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponThere are many tests required in order to release a piece of software. Among the lists of tests that must be run, many of the tests are repeated for each release of the software and possibly repeated even more frequently. Each of those tests has a cost associated with it. Either it costs you time to run the test, or it costs you quality to skip it.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponPerhaps you have looked at how you manually test your application and sorted through all of your tests to select some good candidates for automation. You’ve selected an automated testing tool and have started converting some of your manual tests to scripts. But is the extent of automated testing just to change manual tests into automated ones? Now that you’ve embraced automated testing, what can you do now that you couldn’t do before?
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponOne decision you may find yourself having to make when beginning automated testing is selecting which of your tests to automate. Automating all of your tests may sound appealing at first, but is both difficult and impractical. Some tests are better suited for manual testing while some make excellent candidates for automated testing.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponA smoke test (in software) is a quick test done after a build has completed successfully, but before QA fully tests it.
Microsoft claims that after code reviews, smoke testing is the most cost effective method for identifying and fixing defects in software.
Because the sooner we find a defect, the cheaper it is to fix it, we use a continuous build process utilizing QA Wizard Pro to automatically perform a smoke test each time a build finishes. This lets developers know right away if something that they checked in recently caused a problem.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
Page optimized by WP Minify WordPress Plugin
