Creating New QA Engineering Dept.
We are looking to expand our QA departments into two sections. First is the analysts - generally doing mostly black box testing. Up until now this has been the whole department. We are looking to develop an Engineering department. They would be in charge of sharing in the code review process, developing testing applications and automating some of the black box testing.
So hopefully, someone here has done something like this. QA is something that I have fallen into, and do not have a lot of experience with it. I would like to start with having the Engineers reviewing the code being developed. I think that it would educate them on the product and decrease the number of bugs in the first place.
Is my thinking faulty?
Any suggestions on starting a formal code review process or helpful sites.
If anyone has done this, how did you get the developers to accept the "intrusion" into their world?
Thanks in advance for the help.
Re: Creating New QA Engineering Dept.
We are doing the same thing, it sounds like we are about one project ahead of you.
Our QA group works on a Windows based product with lots of UI. We have found that automation provides the biggest bang for the buck. We have automated daily build acceptance as well as individual features. For the next project we will be automating as much of the grunt work as possible. We have found that test harnesses are valuable, but most valuable for unit testing before code complete. As soon as the project hits code complete and QA begins working toward alpha there is simply not enough time to continue coding tools and testing the product.
For the next project I would like an 80/20 split of time. Before formal testing begins the engineers spend 80% of their time on tools and 20% on test cases, meetings, etc. Once the formal testing kicks in 80% of their time will be on testing and 20% on maintaining their scripts/tools. That's the plan anyway.
As far as the "intrusion" goes, that will depend entirely on the relationship that dev and QA have. We are beginning to get involved with design and code reviews, so far the dev team has been very receptive to QA being involved.
I know this doesn't answer your specific question, but I hope it helps.