The testing methodology is very important in any organization. This document lays the foundation for the testing group. It’s main purpose is to set consistency and discipline to the testing process. It guides you through the process by defining why testing is being done, who is testing, what is produced during the various phases, and when it testing should be included in a project.
You do not need to state specific names/dates/project specific in this document. Project specifics will be in your test plan/test strategy documents.
Below are some key sections that should be part of your testing methodology:
- Introduction
- Vision
- Cost Benefits
- Quality Assurance (QA) vs. Quality Control (QC)
- Purpose of Testing – Keep in mind that other project team members will see this document so it is always a good idea to state the purpose.
- Phases of Testing
- Types of testing and what phase they are planned to be conducted
- Definitions (Just because you know what a term means doesn’t mean everyone else does)
- Roles & Responsibilities
- Testing Process – State if you will be using iterative/waterfall/agile/etc. State when the testing process begins. NOTE: You should always start the testing process sooner than later.
- State what documents will be reviewed by the testing team
- State what documents will be created by the testing team & what phase(s) in the project lifecycle the documents will be created
- Resources needed
- Maintenance procedures
- Environment breakdown
- What type of testing/task is executed/completed sting phases and what testing will be conducted
- Tools used by the testing team
Are there any other sections that you think should be part of the testing methodology?
