5 Considerations When Adopting Automated Testing
Download as PPTX, PDF0 likes526 views
The document discusses key considerations for adopting automated testing, emphasizing the need for a structured approach that includes framework design, balancing different test types, and ensuring cross-team involvement. It highlights common issues like slow execution and maintenance challenges while advocating for practices such as regular reporting and treating test automation as a product. For successful implementation, it stresses the importance of understanding the business and maintaining a focus on quality and efficiency in testing.
5 Considerations When Adopting Automated Testing
- 1. 5 Considerations When Adopting Automated Testing By Bhupesh Dahal Columbus ATDD 11/06/2014
- 2. Who am I ? & Why am I here?
- 3. Agenda • Background- Why test automation ? • Define Problem - Issues most organizations face with test automation • Fixing the above issues, things to keep in mind if you are just starting test automation • Review
- 4. Why Test Automation? Dev Team’s Perspective • Increase effectiveness, efficiency, and coverage of software testing. • For regression testing • Improve quality Boss’s Perspective • Reduce operational cost • Increase revenue
- 5. Blessings from boss to start UI test automation
- 6. What’s the problem eh ? • Test execution is slow • Maintenance takes way too much time • Tests are fragile • Tests are not reusable • Needs more infrastructure • Needs more skilled resources
- 7. Test automation gone wild, boss not happy!
- 8. Framework Design • Do basic meta-programming and start automation—don’t design the entire framework right away • Re-factor often • Understand the business before designing the framework • Abstraction • Have multiple branches • Review test automation architecture regularly • Have a designated Test Automation Architect
- 9. Find a balance between Unit, API Layer and GUI tests • Prioritize Unit and API/Service test automation • Limit the number of GUI tests, have a fixed number of stable end-to-end tests • It’s ok to use multiple technologies • It’s ok to use Record/Play tools like Selenium IDE for throwaway tests • It is better to have 50 stable test cases than 500 fragile ones that breaks regularly
- 10. Reporting/Visibility • Report results from day 1 • Integrate smoke tests with CI build • Run entire suite daily • Store results on a common location that everyone can access • Email results to the entire team-automate email feature • Use tags and map test case/requirements that have been automated • Implement code review
- 11. Cross-Functional Team Involvement • Request BA’s and product owners to review your automated gherkin often • Time box and rotate maintenance tasks with developers and manual testers • Pair up with manual testers when writing different scenarios
- 12. Treating Test Automation as a Product • Test automation will have bugs • Refactor often • Work on tech debt cards regularly in smaller chunks • Make it part of development and definition of done
- 13. Review • Framework • Finding balance between unit, API and GUI tests • Reporting/visibility • Cross-team involvement • Treating test automation as a product You need each of these for test automation project to succeed. Missing one would be like loosing a limb.
- 14. Stay connected www.linkedin.com/in/bhupeshdahal/ Thank you!