1. Test Automation Steffen Goerlitz Barry Lange Mitchell Meerman Harry Schultz Trevor Spees

2. What is test automation? “In software testing, test automation is the use of special software to control the execution of tests and the comparison of actual outcomes with predicted outcomes.” – Wikipedia, 12/06/2015 Test automation is used to automate tasks that happen often where a test process is in place, or a process that would be difficult to do manually.

3. THE AUTOMATED TEST LIFECYCLE METHODOLOGY (ATLM) structured methodology geared toward ensuring successful implementation of automated testing

4. Advantages of Automation Test faster Testing a string table with a program would always be quicker than by hand. Test more Faster testing allows for broader testing scope. Machines can find defects a human technician either may not look for or accurately be able to test.

5. Advantages of Automation Potential observations: Fixable bug finding rate Find rate spikes Fix rate Testing being made possible Nightmares averted Test cycle time

6. Advantages of Automation Potential observations (cont.): Development and test cycle time Management confidence Technical support costs Customer retention Reputation Delivered solutions

7. Disadvantages of Automation GUI test procedures may not survive some development styles e.g. Agile, Extreme Programming, etc. Additional code must be maintained Technicians may adapt to changes in test procedure rather than changes in the tested program Automated testing may miss things that a human tester would be able to find

8. Disadvantages of Automation Very expensive In some cases, automation is not cost-effective Regression testing and reduced test time helps offset the cost Not everything can be automated e.g. password input

9. Types of Automation GUI testing API testing Black box testing Data-driven testing

10. What should be tested? Product installation Test data creation GUI interaction Problem detection Defect logging

11. Types of Automated Tests Code Auditing Coverage Monitor Functional Tests Load Tests Test Management

12. Code Auditing Automatic qualification testing Ensures compliance of code to specified standards

13. Coverage Monitor Determines quantitative measure of code coverage when tests are ran. Very valuable for white-box testing

14. Functional Tests Aimed at examining overall functionality of the product Replaces manual black-box testing Only focuses on externally visible behavior

15. Load Tests Testing the application under heavy loads and measures response. Can simulate many aspects Change of hardware Change of scenario Virtual events

16. Test Management Involves people carrying out tests and correcting the detected errors This test monitors performance of every item on test case files

17. Test Automation in Extreme Programming Test-driven development (TDD) Write a failing test, then write code that will pass the test Regression testing Test automation fits well into regression testing and is performed frequently in XP

18. Test Automation in Extreme Programming From the report Agile Test Automation by James Bach: One “toolsmith”, or dedicated programmer, should be appointed to the testing team Provides tool support for entire test project, not just test execution Reports to requests made by testers Solutions valued based on how much they help testers and test managers perform their jobs Focus on short term testing

19. Toolsmith’s Duties in Test Automation Respond rapidly to requests for assistance from testers Seek out test productivity problems Investigate possible solutions in concert with testers Apply technology to improve the test process

20. Toolsmith’s Duties in Test Automation Advocate for specific testability features in products Research available tools and learn how to use them Gather tools that developers or testers produce Review upcoming product plans to assess automation possibilities

21. Risks to Consider with Agile Automation Testers must be familiar with testing or automation will not cause significant improvements in productivity The number of test cases created or executed in a day can be very misleading and can lead to the number of tests more important than the errors that the tests find. Testers may not want to work with technicians. Cooperation is paramount or the system will fail.

22. Risks to Consider with Agile Automation Technicians may deliver testing solutions that are too maintenance intensive when compared to the value they provide The technicians won’t be the end-all for test innovation; cooperation will help pool the knowledge to be able to create efficient and effective test solutions.

23. Conclusion Test automation lets you test more software faster Really good for regression testing but must be careful how it’s implemented Only worth using in Agile if implemented in fewer than 40 man-hours When used properly, it helps create better quality software

24. Sources Bach, J. (2003, December 1). Agile Test Automation. Retrieved December 6, 2015, from http://www.satisfice.com/articles/agileauto-paper.pdfhttp://www.satisfice.com/articles/agileauto-paper.pdf Haria, M. (2009). Automated Software Testing. Retrieved December 6, 2015, from http://www.cs.nott.ac.uk/~pszcah/G53QAT/Reports09/mxh06u/QAT09Report- mxh06u.doc http://www.cs.nott.ac.uk/~pszcah/G53QAT/Reports09/mxh06u/QAT09Report- mxh06u.doc