How does your daily schedule operate in its normal state?
Is there an equilibrium or testing is merely squeezed between other things?
Curious to know how it is across different teams and companies.
1 Like
Hi @ramanan49,
Honestly, the balance often tilts away from hands-on testing.
A typical day has the morning scrum, then an EOD call that revisits the same updates, followed by client discussions, user calls, and internal syncs.
On top of that, QA work requires documentation; release notes, filing states, gap analysis which is just as critical as execution. Testing time often gets squeezed between these commitments, sometimes less than half the day. The equilibrium isn’t perfect, but the reality is that communication and reporting are part of quality too; the challenge is carving out uninterrupted blocks for meaningful testing.
This came up a while ago but did not get much feedback even though I think it’s really important to understand others roles and views. My target would be 80 percent session based testing if I could, I’m sort of of the view anything that takes me away from testing should be streamlined.