Automated testing coverage (Brainstorm (Question: Why does the manual…
Automated testing coverage
Question: Why does the manual testing cycle take "longer"?
Size of the QA team; dev/QA ratio
Multiple tickets in play?
We have processes where we have to wait for a result before we can continue
Writing automated tests takes
longer than writing the actual dev work
Underestimation of how long it take to write an automated test
1 QA pairing with multiple devs
First time we see many pieces of work is when the work is dev complete
Move the qa left and coach developers on what needs to be tested
Do we need manual testing?
Current status quo: time constraints prevent from implementing the automated testing necessary and that gets complemented by manual testing
Biggest issues and the issues in Production are found by exploratory testing
Manufacture test data is time consuming
On a more broader view: test data management
We suffer from a communication dysfunction
Some processes from InLife work with test data that is very far removed from the production data
No easy way to identify what tests cover a particular area of the system
3 amigoes and pair with developers to define/refine the acceptance criteria and type of tests needed