Skip to main content
Software Quality Assurance & Testing

Return to Question

Tweeted twitter.com/StackSQA/status/795518306673455104
edited title
Link
Michael Durrant
Michael Durrant
  • 25.2k
  • 3
  • 41
  • 113

How to deal with a situation where a team has only 2write automation when test engineers and ask of the time (all the time) isare constantly pulled to do manual testing?

Restructure formating
Source Link
Niels van Reijmersdal
Niels van Reijmersdal
  • 32.6k
  • 4
  • 59
  • 125

The scenario:

  1. Scrum team consists of more developers than testers
  2. Stories revolve around 80% of testing tasks
  3. 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
  4. Though ideally the product manager would let add technical user stories for QA too, most of the times, such automation backlog stories dont get prioritized over other testing tasks
  • 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
  1. 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: 1One of the things we did was ask our Developers to help complete automation (on a feature they haventhaven't coded for). However, 2two things happen due to this:

  1. QA does not get a chance to improve automation skill set
  2. 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?

How to deal with this contradictory situation?

The scenario:

  1. Scrum team consists of more developers than testers
  2. Stories revolve around 80% of testing tasks
  3. 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
  4. Though ideally the product manager would let add technical user stories for QA too, most of the times, such automation backlog stories dont 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: 1 of the things we did was ask our Developers to help complete automation (on a feature they havent coded for). However, 2 things happen due to this:

  1. QA does not get a chance to improve automation skill set
  2. 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?

The scenario:

  1. Scrum team consists of more developers than testers
  2. Stories revolve around 80% of testing tasks
  3. 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
  1. 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:

  1. QA does not get a chance to improve automation skill set
  2. 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?

Source Link
shanianp
shanianp
  • 81
  • 1

How to deal with a situation where a team has only 2 test engineers and ask of the time (all the time) is manual testing

The scenario:

  1. Scrum team consists of more developers than testers
  2. Stories revolve around 80% of testing tasks
  3. 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
  4. Though ideally the product manager would let add technical user stories for QA too, most of the times, such automation backlog stories dont 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: 1 of the things we did was ask our Developers to help complete automation (on a feature they havent coded for). However, 2 things happen due to this:

  1. QA does not get a chance to improve automation skill set
  2. 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?