You have just finished building your business Web sites. You've proven yourself and other employees had the test company. The website now goes live. A few weeks after starting to receive emails from angry customers who complain they can not place orders because certain steps in the "Buy Now" to process errors. Quickly solve the problem. A few days later you complain about something and others again react quickly to fix the website. This continues for a few months until the complaints stop order and stabilize things. At this point, make some improvements to your website. A few days later, an email client tells the fact that in the process of making this improvement was "broke" something more on the website. Once you spend time to find and fix the problem, but is currently not a little perplexed and frustrated. These issues have cost many customers in recent months and potentially ill-will spread throughout the broader community of customers. It seems to you that the only way of detecting these problems before they went "live" have employed a large army of testers, which your company can not afford.
Enter automated software testing. While nothing can replace a good human testers, test coverage requires a certain degree of automation software to be economically viable. Automated testing tools can provide a large labor force multiplier and a very good job complementing human testers. All changes to your website, no matter how small requires testing to make sure that nothing else was affected. This becomes very quickly a long time due to the large number of possible test cases. A strategy by which the tests are performed automatically with the software becomes an economic necessity.
There are two kinds of automated testing tools. The first type tools, functional and regression testing, helps to ensure that the site behaves as expected: for example, if a customer clicks the X button, and the page displays no errors. Tools for functional testing and regression are able to automate a large number of scenarios to ensure that your website works as intended. The second type, load test tools gauge how well your website performS when subjected to a great effort as a large number of simultaneous users. I will be discussing the load tests in a separate article.
Now I will give an overview of the basic features of functional testing. Before starting any kind of functional test automation is needed to identify the test scenarios that want to automate. Once done, you have to generate test scripts that cover these scenarios.
A typical functional testing tool record user interactions with a website. As you perform various operations on your website or application, the tool records each step. When finished recording, it generates an automated script for your interactions with your website. Another possibility is to use the tool to build the script together. Testers normally tend to do a combination of both. Recorder is used to generate the basic framework of their scripts and then set the scripts by hand to incorporate special cases.
Scripts can be graphic and / or text-based in nature. A good functional testing tool does not require users to have a programming background. Users who are not fluent in programming will mainly work with storyboards. In most tools usually storyboards show all interactions in a tree structure and users can edit any node in the tree to change the script. Some users, however, that have programming background may wish to program their scripts. These users typically work with a script written text in a standard language such as JavaScript or VBScript.
Once you have created the script will have to insert the controls in scripts to test whether your site is working properly. These controls are called checkpoints. A checkpoint verifies that the property values ??obtained by studying the site to coincide with the expected values. Checkpoints allow you to define criteria to compare expected values ??with the values ??obtained. The expected value of a property is derived from the recording of interactions with the website. This view and modify the control points. The current value is retrieved during playback (ie during the execution of the test case).
There are many different types of checkpoints. A checkpoint verifies the source page of a page or frame, as well as their statistical properties. You can check for broken links, check the link URL, image sources, the hierarchy of HTML tags or even the entire HTML source of Web page or frame. You can also set thresholds for the load time of a page. A text checkpoint checks that a certain text is displayed or not displayed in a specific area on a website. A Web object checkpoint checks the web object properties, for example, the value of an HTML input field. A checkpoint database checks the contents of a database used by your website.
When you play a test script, testing tool will open the registered application and follow the steps recorded in the same order they were specified in the script. As you play the script will also run through all the checkpoints have been inserted into the script. In addition, you can test the behavior of your application with different data inputs. For example, you can try to submit a page after entering different values ??in the edit box of a website. At the end of reading a detailed report is usually generated.
functional test automation allows you to automate repetitive tests of a large number of scenarios through its website. functional testing tools are an important weapon in their arsenal whose use development provides a large increase in productivity and allows small groups of tests to perform much work. There is a strong economic argument for the use of functional testing tools as part of the development cycle and deployment of a website.
Topic: Automated Website Testing (Read 1120 times)
