| || |
Standards for Release
I have been tasked to come up with a set of Quality Standards. What this means (in my company) is what is expected of development before QA will accept code. We have developed some bad practices of accepting code before any technical documentation has been written.
Because of this, we spend our valuable test time deciphering exactly what it is we are supposed to be testing.
Any comments or help would be very much appreciated.
As always I understand the obvious answer (don't accept the code unless it is complete), but we all know how management thinks on this subject. So I would like to set up some procedural rules.
Re: Standards for Release
Try searching the forums for the following topics:
- entrance criteria from dev to test
- exit criteria from test to production