How many problems do you have to solve if you are atqa engineer

1. How many problems do you have to solve
if you are ATQA engineer

2. To be or not to be?

3. Problem solving
• Try to understand following factors:
• Project duration
• Configuration testing
• Amount of routine work
• Frequent releases

4. Automation framework
VS

5. Problem solving
• Find stakeholders
• Define metrics
• Time to create tests
• Time to update tests
• Execution time
• Flexibility of automation tests

6. Programming language

7. Problem solving
• Understand value if:
• Language of ATQA team == Language of developers team
• Language of ATQA team != Language of developers team
• Factors:
• Time for creating/updating tests
• Teams collaboration (ATQA + Dev)
• Responsibility for the choice of technology

8. Lack of visibility

9. Problem solving
• Defining metrics for the client
• Number of covered business rules
• Percent Automatable or Automation Index
• Technical solutions
• Integration with test management systems
• Readable reports

10. Slow execution time

11. Problem solving
• Define thresholds for execution time
• Test selection
• Run test in parallel
• Selenium Grid
• Testing framework (TestNG, JUnit)
• Pre-conditions can run faster

12. Requirements can be changed
When the customer
sent changes in the requirements

13. Problem solving
• Increased team expertise in business
• Participation in refinement, planning, estimation sessions
• Collaboration with manual QA
• Traceability Matrix
• Technical solutions
• Marking tests using annotations

14. Coverage by auto-tests
Pinocchio never understood why his nose
grew whenever he talked about coverage
I've executed all
the tests so we have
100% coverage now

15. Problem solving
• A good quality is NOT 100% coverage
• Refine the coverage metrics
• Acceptance criteria
• Manual test cases
• Code
• Create corrective actions for uncovered business rules

16. Flaky tests

17. Problem solving
• Reliable pre-conditions and post-conditions
• Independent tests
• Correct use of waits
• Re-running flaky tests on CI
• Flaky test handler plugin

18. Conclusion