Which testing phase takes the longest in your process?

General Discussions
, ,
1

We spent 5 hours this week trying to debug a flaky test on a staging environment.

It got me thinking, in your testing workflow, which phase actually eats up the most time? I used to think it was test execution, but lately… debugging is the real black hole.

:point_down: Cast your vote, and drop a comment if you’ve got a story to share.

  • Test Planning
  • Test Execution
  • Test Reporting
  • Debugging

0 voters

For me, debugging always throws a surprise. A small selector change caused 20 test failures last week :upside_down_face:

What’s your “longest phase” horror story?

2

I opted for Debugging cause definitely takes the longest in our process.

Test execution is usually fast thanks to automation, but when something fails, especially due to flaky tests or minor UI changes, debugging becomes a time sink.

You end up checking logs, re-running tests, verifying environments, and sometimes pulling in developers to isolate the issue.

It’s not just about fixing the test, but understanding why it failed in the first place. That’s what really slows things down.