How many developers do realize, it is a Tester, who acts as a customer, when an internal release is taken for testing?
How many testers realize that they need to help the developers after rejecting a build for testing?
Are the above questions essential for you?
While you try to answer the above questions, I would want to help you with some gyaan**, I got, either through someone or through mistakes.
_ The first customer is always a tester _
I have had an experience of rejecting a few releases that were made to me for testing, before releasing it directly to the customer. Yes, I did my job well, so did I reject the release.
Sometimes, it so happens, you have to wait for your managers approval to reject a release and there is nothing wrong in it, since, we are not in those loops, which has the discussions of business needs and customer dissatisfaction.
I need to tell you, when can we(testers) reject a build?
- Reject a build/release, if it fails in BVT (Build Verification Test)
- Reject a build/release, if it even fails to install on the target.
- Reject a build/release, if it fails to come up after the installation.
- Reject a build/release, if it fails in core functionality.
- Reject a build/release, if the bug, which was supposed to be killed, is alive and active.
- Reject a build/release, if the previous working features, works more with bugs.
- Reject a build/release, if there is no time to test, even basic functionality.
- Lots more... (context based)
I also need to tell you, what is the way to reject a build?
- Before you reject, ensure, you have solid proof to support rejection.
- Before you reject, go through pointers from the test plan, which has the criteria to reject.
- Before you reject, state it clearly in the mail you draft, as to , why you think it can't be tested?
- Before you reject, discuss it, informally, with the developers/testers/lead/manager. Don't give them surprises.
- Before you reject, plan on the help, you are going to provide the developers/management, in an effort to make the next build, a better quality one.
- The mail you draft should be soft and not in a way that, you are pointing finger on a particular developer.
- Be a good customer, to a developer.
I should not forget to tell you, What should you do after rejecting a build?
- Sit with the developer, work a way out to fix the blocking issue, provided, he/she needs help and is comfortable, working, while having you next seat.
- Engage yourself, in an activity, preparing for the next release.
- Request the developer, to review his unit test cases. As of now, I would put it in a way like this "Hey XXXX, there have been wonders when a fool looks at something, similarly, I would like to do a wonder with your unit test cases, would you want to witness it?
- Utilize the time, you may have, after rejecting a build/release, in improving yourself.
_ End of _The first customer is always a tester _
"Dont feel bad when she rejects your love, just because you rejected her build"
Thanks and Regards,