You just completed creating your company's web-site. You have tested it your self and had other firm personnel test it. The web-site now goes reside. A handful of weeks later you get started acquiring emails from irate clients who complain that they are unable to location their orders for the reason that specific steps in the Obtain Now procedure give errors. You easily repair the situation. A handful of days later you get complaints about some other concern and you once again react easily to repair the web-site. This continues for a handful of months till the complaints finally halt and issues stabilize. At this point you make some enhancements to your web-site. A handful of days later a buyer e-mail alerts you to the fact that in the procedure of creating this enhancement you broke a thing else on the web-site. Once more you spend time to locate and repair the situation but by now you are perplexed and not a small frustrated. These problems have expense you plenty of clien ts in the final handful of months and potentially spread ill will across the broader buyer community. It appears to you that the only way to have detected these problems prior to they went reside was to have employed a huge army of software package testers, a thing your firm is unable to afford. Enter automated software package testing. Even though absolutely nothing can replace good human testers, broad test coverage needs some degree of software package automation for it to be economically feasible. Automated testing tools can give a substantial workforce multiplier and do a rather good job complimenting human testers. Just about every modify to your web-site no matter how little needs thorough testing to make certain that absolutely nothing else was affected. This becomes rather time consuming rather easily due to the huge quantity of doable circumstances to test. A method whereby tests are automated employing software package becomes an economic necessity. There are two classes of automated testing tools. The 1st kind, functional and regression testing tools, helps to make confident that the web-site behaves as it will need to: for instance if a buyer clicks on button X, page Y is displayed with out errors. Functional and regression testing tools are in a position to automate a huge quantity of scenarios to make certain that your web-site functions as intended. The second kind, load testing tools gauge how well your web-site performs when subjected to a huge tension, such as a huge quantity of simultaneous users. I will be discussing load testing in a separate report. I will now give you an overview of the standard characteristics of functional testing. Ahead of you can begin any kind of functional test automation you will have to have to identify the test scenarios you wish to automate. When this is done, you will have to have to create test scripts that cover these scenarios. A functional testing tool will generally record user interactions with a web-site. As you execute different operations on your web-site or application, the tool records every step. When you finish recording, it generates an automated script from your interactions with your web-site. Alternatively you could use the tool to construct the script by hand. Ordinarily testers tend to do a combination of the two. They will use the recorder to create the standard framework of their scripts and then tweak the scripts by hand to incorporate particular circumstances. Scripts can be graphical and/or text based in nature. A good functional testing tool does not require users to have a programming background. Customers not proficient in programming will perform predominantly with graphical scripts. In most tools graphical scripts will generally show all interactions in a tree structure and users can edit any node of the tree to modify the script. Some users in spite of this, who have programming backgrounds may very well wish to plan their scripts. These users will generally perform with a text script written in a typical language such as JavaScript or VBScript. When you have generated your script you will have to have to insert checks in your scripts to test if your web-site is functioning appropriately. Such checks are normally called checkpoints. A checkpoint verifies that values of a property obtained when testing the web-site match expected values. Checkpoints allow you to set the criteria for comparing expected values with obtained values. The expected value of a property is derived from recording interactions with the web website. It is viewed and modified from checkpoints. The present value is retrieved during replay (i.e. during the execution of the test case). There are plenty of various sorts of checkpoints. A page checkpoint verifies the source of a page or frame as well as its statistical properties. You can examine for broken links, verify link URLs, image sources, the hierarchy of HTML tags or even the complete HTML source of the Internet page or frame. You can also set thresholds for the loading time of a page. A text checkpoint verifies that a given text is displayed or is not displayed in a specified region on a web page. A web object checkpoint verifies the properties of a web object e.g. the value of an HTML INPUT field. A database checkpoint verifies the contents of a database utilised by your web-site. When you replay a test script, the testing tool will open the recorded application and execute the recorded steps in the exact same sequence they had been specified in the script. As it replays the script it will also run by means of all the checkpoints you have inserted into the script. In addition, you can test your applications behavior with varying information inputs. For instance you can attempt to submit a page right after entering various values in the edit box of a web page. At the end of the replay a detailed report is generally be generated. Functional test automation permits you to automate the repetitive testing of a huge quantity of scenarios across your web-site. Functional testing tools are an significant weapon in your development arsenal whose use supplies a substantial productivity gain and permits for little testing groups to achieve significantly even more perform. There is a rather strong economic case for the use of Functional Testing Tools as part of the development and deployment cycle of a web-site.
No comments:
Post a Comment