What do you think is the most difficult aspect of testing in Agile development?

We had to rework two test cases twice this sprint due to shifting requirements.

It got me thinking in Agile teams, what do you find most difficult when it comes to testing? I used to think it was just short sprints, but lately… It’s the constant changes that break things mid-way.

:point_down: Cast your vote, and feel free to drop a comment if you’ve hit similar walls.

  • Frequent changes :infinity:
  • Short sprint timelines :running_man:
  • Managing tech debt :briefcase:
  • Dev & QA collaboration🤝

0 voters

Frequent changes, no doubt. Last week, we locked test cases on Tuesday, and by Thursday, the user flow had already changed. Hard to keep pace when the goalpost keeps moving :sweat_smile:

Anyone else struggling with this, or have a way to stay ahead of scope shifts?

I agree, @kavitajoshi. Frequent changes are the toughest part for us. We finalize test scenarios, and then requirements shift mid-sprint, causing rework, invalid tests, and misaligned priorities.

It’s Agile, so change is expected, but it’s definitely the hardest to keep up with from a QA standpoint. I did vote for Frequent changes ofc.

Ask ChatGPT