Answer the question
In order to leave comments, you need to log in
How to solve the problem of a critical bug before the release?
Hello!
Interested in the opinion of the community on the question that recently caught on the interview.
I would appreciate any opinion.
Team: Scrum
Problem: Found critical bug late Sunday evening, release Monday morning.
Who to contact: Scrum master, several developers from the team.
Question: What should the tester (you) who discovered it do?
Answer the question
In order to leave comments, you need to log in
Well, this is a question of the coincidence of the value system, so you need to understand what values the hiring people are trying to convey to the hired ones.
If they appreciate the readiness to close the embrasure with their chest, then "Raise to their feet everyone I can get through and get them to fix everything."
If they love their beautiful processes and instructions, then "I will do as it is written in the Comprehensive Instruction for the Tester from our Dear Technical Director."
If you like to read books, then, probably, in some book about Scrum there is some pretentious advice about this - maybe sit down to play poker or something like that. Or even figure out how to fix it yourself.
Well, life's advice, of course, is not to look for bugs on Sunday late at night. This is unreasonable.
Get enough sleep to get to work on time and prevent the release of a broken version of the product. At the retro, agree on steps to prevent this from happening again, as well as clearly raise the issue of the inadmissibility of testing on the weekend - everything must be done before the end of the working day on Friday! You need to rest on weekends.
There is only one correct answer - write a bug to the ticket holder with the appropriate priority (highest) and assign it to the appropriate person; add everyone you need to observers. Everything.
And what kind of cockroaches are in the heads of those to whom you went for interviews, and what answer they consider to be correct - we cannot find out in any way.
I’m not talking about what the hell testing is done after hours and on the night before the release))
If everything is running like that, then we can assume that it’s all not important at all and nothing bad will happen if the release is postponed in the morning.
Where such releases are *really* important, they don't test the night before the release.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question