- Scrum team consists of more developers than testers
- Stories revolve around 80% of testing tasks
Why so much testing?
- There are asks of E2E testing for several user flows; regression testing for some on E2E level
- most of which changes at upstream / UI so that automation is not an option always; component level new features being added and need feature testing; automation of these tests; Documentation
- because the areas of testing and steps often encompass new domains and complicated environment setups
- Though ideally the product manager would let add technical user stories for QA too, most of the times, such automation backlog stories don't get prioritized over other testing tasks
Due to the above, most of the times, the QA need to concentrate on a lot of manual testing. And hence, automation goes to a backseat. Sometimes the features need to be pushed out so much soon, that the automation gets a backseat.
Question 1: In these circumstances, how can a team manage coping up with automation?
Question 2: One of the things we did was ask our Developers to help complete automation (on a feature they haven't coded for). However, two things happen due to this:
- QA does not get a chance to improve automation skill set
- As QA does not do automation anymore, (the criteria of performance reviews) the QA gets negatively impacted during the evaluation
How to deal with this contradictory situation?