| || |
Starting to work on the SW Testing
I'm going to work on the software testing process for a company, which has several projects (with uses different technologies), and I'm planing to improve and automatize the software testing process. I know some of the concepts such as black box and white box testing, and some of its techniques, but I do not have much experience in the field. I'm going to have access to the projects documentation, and I expect to be involved more with functional testing, rather than white-box testing (alhough I'm not entirely sure).
What's the "right way" to start? I know that it depends on several factors, so I don't expect to get a perfect answer, but if I could read how others start, it would be great for me.
What sort of guidelines do you follow from the start? Where do the CMMI and IEEE829 standards come in? Are the any other standards/guidelines worth of note?
What's the best way to make a correct assessment of the current efficiency/productivity level of the software testing process inside the company?
Testing processes is a big field and below are some aspects that you can focus on.
At a high-level, you can start with:
A) Understand the existing process framework within your org
- Access the process methodologies, templates which directly relate to quality assurance.
- Understand the process flows as given in the methodologies.
- (most important) Understand the overall benefit of the process to a team.
B) Review the processes adopted by various projects in your org
- Check how many of the org processes are "adopted" and how much is "customized" based on the need of the projects.
- Review if the existing processes give value to the team and the project?
- You need to go through the complete SDLC for the projects to understand process impacts and its value to the project.
C) Assess and optimize the processes
- Assess the process methodologies at the org level and optimize these from 3 angles: 1) Review feedback from the project customizations going on in the org, 2) Review feedback from your own assessment - based on adoption of the org processes by the projects & 3) Review feedback based on a study done for the CMMI/IEEE standards and external sources.
- Create reports based on the above steps and provide optimization suggestions / action points.
- Work with project management at various levels to take inputs and optimize processes (by taking out the unnecessary ones and adding the required ones).
Simple yet effective.Thanks for valuable information.
Originally Posted by Andy79