The 30 Days of Agile Testing Day 30 task is:
Contribute to The Club how your team reacts to a build that has gone red
How does your team approach this?
The 30 Days of Agile Testing Day 30 task is:
Contribute to The Club how your team reacts to a build that has gone red
How does your team approach this?
Not proud about this answer!
Today we had a red build, failed on Cypress step on a feature branch.
All Cypress tests were OK but I added (few weeks ago) a failed status for any error log during Cypress step. I called a dev “it seems that a property does not exist on your feature” (it was explicit on the log). His final answer: “You have to add the property on docker compose”.
This conversation pissed me off. Does someone in my team is looking why the build is red? Why nobody tell me the existence of this property? Have I to complete the docker compose (may be, but never identify this task)?
Is it a communication problem? Is it a quality implication problem? I do not know what to think…
Usually when something is failing in the CI and it’s impacting, we’ll either get alerts or teams would be notified via community slack messages. When this happens, a number of devs will investigate, find the root cause and implement a quick fix.
Devs are trying to locate the problems and then come up with good solutions while testers investigate the rules of the builds and trying to understand them. Then idea is to communicate with developers and benefit their process of generating a solution
Dev or tester gets notified and discusses with whoever pushed most recently. If needed that person gets some help solving the issue right then and there as well.