I have searched several of the IEEE, CMM(I), etc. documents/standards with the hopes of finding a documented standard or recommendation on who should review/provide input to test cases written by an independent SQA organization.
Background:
The SQA Organization writes test cases/plans based on the requirement document(s) provided by the Systems Engineering organization. They (SQA) ensure that all requirements are covered in the test cases (traceability). When it comes to reviewing/baselining the test case document, only the SQA organization is involved.
They (SQA) feel that making the test case document(s) available to Development is not a good idea – since they (Dev) could potentially execute this test plan during software development, fix any potential bugs, and deliver the code. By the time SQA comes to execute these same test cases, they will obviously all pass — so what value is the SQA organization adding? Why not ship the software right at the end of the development cycle?
Question:
Is there any documented or suggested CMM(I)/SixSigma standard/guideline that specifically deals with test planning and test case documentation AND whom (from the SDLC) should/must be involved in reviewing and approving test cases for software projects? Anything that is specific as to whether sharing the test cases/plan with the overall team is a good idea or not and whether it should be or shouldn’t be done?
I understand that there are pros and cons to sharing the test cases – but what is the “standard” or guideline(s)?
.
