1

I am working as an associate QA engineer and my team asked me to send a QA confirmation email. I don't have any experience with a confirmation email.

Can you tell me what the format for a QA pass email is? I've tried Google, but can't find any help on formatting - maybe my keywords are wrong.

I read this article but it does not help me.

  • Beyond the format, you may want to consider whether such a "sign-off" email is really a good idea, for you, the team, or the company, especially if it might be taken to mean that there aren't any problems, then used against you when problems are found after release. This 12-minute interview with Michael Bolton might be helpful in clarifying the purpose of such communication or alternatives: youtube.com/watch?v=YM3XOqdeb2o – c32hedge Feb 25 at 17:51
6

I never heard of any formal artifact of that name but if you go with a simple test report I imagine you should be fine. Just write down what (exactly) was tested, where you tested what you found, what your passing criteria were and identify remaining risks. If they need anything else they'll tell you, or even better, just ask them beforehand. Being a good communicator is part of being a good QA Engineer.

  • thank you but they said they need email qa confirm there are no issue with this release its ask by CEO even developer also have no idea about that :( and there are no senior person all people are associate level and trainees – GHOST Feb 15 at 7:13
  • 2
    Well, neither the ISTQB nor IEEE 829 define the format so, from a completely technical POV you could write whatever you want. If you look at this page en.wikipedia.org/wiki/Software_test_documentation you'll see all the standard artifacts of testing. I assume the Master Test Report would be closest to what they need although that might actually be overkill, but that' what happens when people require undefined documents noone can explain.^^ – Daniel Feb 15 at 7:30
  • 1
    @GHOST you could do that while following the advice Daniel gives. Where I work our "sign-off" process is essentially what Daniel says. Lay out any issues you've found, and attach any test results to the email. If there are issues you feel should stop the release, highlight them in the email. If you don't think there are problems, say that testing is completed, there are no known issues and you believe it's ready for release. – anonygoose Feb 15 at 9:12
  • 4
    @ghost In my view it is not your decision whether it is good for release or not. You provide information. So as Daniel stated: list what you have done. What you not have done. What your results are and document the issues you feel are serious and for what reason. It's not your pay grade to decide. So don't be forced in the scapegoat position. Just a word of warning... – Ray Oei Feb 15 at 11:01
  • 1
    Have a read here and here. I concur with the main message: shipping is a business decision not a qa/tester one. – Ray Oei Feb 15 at 14:25
3

In short, there is NO overarching, industry-wide accepted format for a sign-off email (which is what they are asking you to compose). I have been in QA - automated and manual - for almost 25 years now, and have never seen a template for a sign-off email. You and your team would need to make the determination on what is expected in the body of the email. Some teams, "QA signs-off on XXXX" is good enough. Others may be more robust.

TLDR;

Ask your team what the expectation is!

3

Although this doesn't answer the question directly, as there isn't a 'standard sign-off email' at least that I know of, the underlying problem is more important.

As far as I am concerned 'shipping' is a business decision. Not a decision made by the tester/QA or the team. I wholeheartedly concur with this when testers are asked for ship/noship opinion and have a read here.

Your job is to inform. As has been mentioned elsewhere: communicate what you have done, how you did it and what you didn't do. So others can make informed decisions based on what you provided and on information provided by others and information you don't even know exists.

To me it seems as you are being setup to be the scape goat, the fall-guy or at best the 'one to make the decision so no-one else has to'. That is not your role, and I assume you are also not being paid for it.

Originally added as a comment, I added this as an answer on a nudge from @32hedge ;-)

2

Same as Daniel was mentioning above, there is no specific standard set for sending the Testing Sign off email. But what you can do is, is to include the necessary details in the sign off email.

Below items can be optional for your team, so choose the ones you need.

  1. Which feature you are signing off.
  2. Which environment,browser (versions)/application version you have tested the feature.
  3. List of tests you have executed for the feature.
  4. List of tests which were marked as de scoped/not in scope for testing this feature.
  5. Build version of the feature which was tested.
  6. Bugs obtained while doing the testing, its status.
  7. List out the known open bugs which is accepted for this feature.
1

The correct format is the format you and your team/company decide on. Like others wrote there is no industry standard. Actually I think most companies use a workflow management system to handle this, or a test management tool, not email.

Still if email is the way to go, I would suggest you try to find the Minimal Viable Bureaucracy. Whats is the minimal email content that will generate the necessary flow of communication.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.