Test automation

"Automated QA" redirects here. For the company, see AutomatedQA.

Test automation is the use of software (separate from the software being tested) for controlling the execution of tests and comparing actual outcome with predicted. ^[1] Test automation supports testing the system under test (SUT) without manual interaction which can lead to faster test execution and testing more often. Test automation is key aspect of continuous testing and often for continuous integration and continuous delivery (CI/CD). ^[2]

Compared to manual testing

Automation provides many benefits over manual testing.

API testing

For API testing, tests drive the SUT via its application programming interface (API). Compared to manual testing, automated API testing often can execute a relatively large number of cases in a relatively short time.

GUI testing

For GUI testing, tests drive the SUT via its graphical user interface (GUI) by generating events such as keystrokes and mouse clicks. Automated GUI testing can be challenging to develop, but can run much faster than a human could perform the same testing. Specializations include:

• Record & playback testing – Some GUI testing tools provide a feature that allows for interactively recording user actions and replaying them later as a test; comparing actual results to expected. An advantage of this approach is that it requires little or no coding. However, some claim that such tests suffer from reliability, maintainability and accuracy issues. For example, changing the label of a button or moving it to another part of the view may require tests to be re-recorded, and such tests often are inefficient and incorrectly record unimportant activities.^{[ citation needed ]}

• For testing a web site, the GUI is the browser and interaction is via DOM events and HTML. A headless browser or solutions based on Selenium Web Driver are normally used for this purpose. ^{[3] [4] [5]}

Regression testing

When automated testing is in place, regression testing can be a relatively quick and easy operation. Instead of a significant outlay of human time and effort, a regression test run could require nothing more than a push of a button and even starting the run can be automated.

Automated techniques

The following are notable testing techniques categorized as test automation.

Continuous testing

Continuous testing is the process of executing automated tests as part of the software delivery pipeline to asses the business risk of releasing the SUT. ^{[6] [7]} The scope of testing extends from validating bottom-up requirements or user stories to assessing the system requirements associated with overarching business goals. ^[8]

Model-based testing

For model-based testing, the SUT is modeled and test cases can be generated from it to support no code test development. Some tools support the encoding of test cases as plain English that can be used on multiple operating systems, browsers, and smart devices. ^[9]

Test-driven development

Test-driven development (TDD) inherently includes the generation of automation test code. Unit test code is written while the SUT code is written. When the code is complete, the tests are complete as well. ^[10]

Other

Other test automation techniques include:

• Data-driven testing
• Modularity-driven testing
• Keyword-driven testing
• Hybrid testing
• Behavior driven development

Considerations

A review of 52 practitioner and 26 academic sources found that five main factors to consider in test automation decision are: system under test (SUT), scope of testing, test toolset, human and organizational topics, cross-cutting factors. The factors most frequently identified were: need for regression testing, economic factors, and maturity of SUT. ^{[11] [12]}

While the reusability of automated tests is valued by software development companies, this property can also be viewed as a disadvantage as it leads to a plateau effect, where repeatedly executing the same tests stops detecting errors.

Testing tools can help automate tasks such as product installation, test data creation, GUI interaction, problem detection (consider parsing or polling agents equipped with test oracles), defect logging, etc., without necessarily automating tests in an end-to-end fashion.

Considerations when developing automated tests include:

• Platform and operating system independence
• Data-driven testing
• Reporting (database, Crystal Reports)
• Ease of debugging
• Logging
• Version control
• Extension and customization; APIs for integrating with other tools
• Integration with developer tools; for example, using Ant or Maven for Java development
• Unattended test runs for integration with build processes and batch runs
• Email notifications; i.e. bounce messages
• Distributed test execution

Roles

To support coded automated testing, the test engineer or software quality assurance person must have software coding ability. Some testing techniques such as table-driven and no-code can lessen or alleviate the need for programming skill.

Framework

A test automation framework provides a programming environment that integrates test logic, test data, and other resources. The framework provides the basis of test automation and simplifies the automation effort. Using a framework can lower the cost of test development and maintenance. If there is change to any test case then only the test case file needs to be updated and the driver script and startup script will remain the same.

A framework is responsible for defining the format in which to express expectations, providing a mechanism to hook into or drive the SUT, executing the tests, and reporting results. ^[13]

Various types of frameworks are available:

• Linear – procedural code, possibly generated by tools like those that use record and playback
• Structured – uses control structures - typically ‘if-else’, ‘switch’, ‘for’, ‘while’ conditions/ statements
• Data-driven – data is persisted outside of tests in a database, spreadsheet, or other mechanism
• Keyword-driven
• Hybrid – multiple types are used
• Agile automation framework
• Unit testing – some frameworks are intended primarily for unit testing such as xUnit, JUnit and NUnit

Test automation interface

A test automation interface is a platform that provides a workspace for incorporating multiple testing tools and frameworks for system/integration testing. A test automation interface may simplify the process of mapping tests to business criteria without coding. A test automation interface may improve the efficiency and flexibility of maintaining tests. ^[14]

Test Automation Interface Model

A test automation interface consists of the following aspects:

Interface engine

Consists of a parser and a test runner. The parser is present to parse the object files coming from the object repository into the test specific scripting language. The test runner executes the test scripts using a test harness. ^[14]

Object repository

Collection of UI/Application object data recorded by the testing tool while exploring the SUT. ^[14]

See also

• Comparison of GUI testing tools
• List of web testing tools
• Fuzzing  – Automated software testing technique

References

1. Kolawa, Adam; Huizinga, Dorota (2007). Automated Defect Prevention: Best Practices in Software Management. Wiley-IEEE Computer Society Press. p. 74. ISBN   978-0-470-04212-0.
2. O’Connor, Rory V.; Akkaya, Mariye Umay; Kemaneci, Kerem; Yilmaz, Murat; Poth, Alexander; Messnarz, Richard (2015-10-15). Systems, Software and Services Process Improvement: 22nd European Conference, EuroSPI 2015, Ankara, Turkey, September 30 -- October 2, 2015. Proceedings. Springer. ISBN   978-3-319-24647-5.
3. Headless Testing with Browsers; https://docs.travis-ci.com/user/gui-and-headless-browsers/
4. Headless Testing with PhantomJS;http://phantomjs.org/headless-testing.html
5. Automated User Interface Testing; https://www.devbridge.com/articles/automated-user-interface-testing/
6. Part of the Pipeline: Why Continuous Testing Is Essential, by Adam Auerbach, TechWell Insights August 2015
7. The Relationship between Risk and Continuous Testing: An Interview with Wayne Ariola, by Cameron Philipp-Edmonds, Stickyminds December 2015
8. DevOps: Are You Pushing Bugs to Clients Faster, by Wayne Ariola and Cynthia Dunlop, PNSQC October 2015
9. Proceedings from the 5th International Conference on Software Testing and Validation (ICST). Software Competence Center Hagenberg. "Test Design: Lessons Learned and Practical Implications. doi:10.1109/IEEESTD.2008.4578383. ISBN   978-0-7381-5746-7.
10. Vodde, Bas; Koskela, Lasse (2007). "Learning Test-Driven Development by Counting Lines". IEEE Software. 24 (3): 74–79. doi:10.1109/ms.2007.80. S2CID   30671391.
11. Garousi, Vahid; Mäntylä, Mika V. (2016-08-01). "When and what to automate in software testing? A multi-vocal literature review". Information and Software Technology. 76: 92–117. doi:10.1016/j.infsof.2016.04.015.
12. Brian Marick. "When Should a Test Be Automated?". StickyMinds.com. Retrieved 2009-08-20.
13. "Selenium Meet-Up 4/20/2010 Elisabeth Hendrickson on Robot Framework 1of2". YouTube . 28 April 2010. Retrieved 2010-09-26.
14. "Conquest: Interface for Test Automation Design" (PDF). Archived from the original (PDF) on 2012-04-26. Retrieved 2011-12-11.

General references

• Elfriede Dustin; et al. (1999). Automated Software Testing . Addison Wesley. ISBN   978-0-201-43287-9.
• Elfriede Dustin; et al. (2009). Implementing Automated Software Testing. Addison Wesley. ISBN   978-0-321-58051-1.
• Mark Fewster & Dorothy Graham (1999). Software Test Automation. ACM Press/Addison-Wesley. ISBN   978-0-201-33140-0.
• Roman Savenkov: How to Become a Software Tester. Roman Savenkov Consulting, 2008, ISBN   978-0-615-23372-7
• Hong Zhu; et al. (2008). AST '08: Proceedings of the 3rd International Workshop on Automation of Software Test. ACM Press. doi:10.1145/1370042. ISBN   978-1-60558-030-2.
• Mosley, Daniel J.; Posey, Bruce (2002). Just Enough Software Test Automation. Prentice Hall Professional. ISBN   978-0130084682.
• Hayes, Linda G., "Automated Testing Handbook", Software Testing Institute, 2nd Edition, March 2004
• Kaner, Cem, "Architectures of Test Automation Archived 2021-01-26 at the Wayback Machine ", August 2000