>I disagree. QA should test new code functionality and issues in each build (if it builds successfully of course). :o) Apparently we do it differently. :o)
>

Tracy,

In our environment a developer reviews the code written by the other developer. Then the application is built, then it is send to QA team. Then it can come back to the developer to fix things or go to the documentation abd be included into the final build.

>>I disagree. Here are the three things I listed:
>>
>>- Local builds should be per developer and should only affect the .exe in the development environment
>>- Build servers should build and test your application, then report back the results.
>>- Once results are satisfactory and pass all tests with all new functionality, you can build a release version.
>>
>>The first item is done locally by each developer. No QA involved. The middle step is done automatically on the build server. QA does not do anything until the third item passes.
>>
>>
>>>I agree with Craig. The same process should be adhered to for all apps. Just a note, QA tests in all three stages he listed and it doesn't pass to go on to the next phase until that occurs. Regression testing falls into that as well... No matter how simple the app, it's important. The simpler the app, the quicker the testing.
>>>