Quality Assurance and Compliance is a policy document which is at the top of the hierarchy of the Test Documentation Structure. A QA Policy document represents the testing process of Netlink as a whole and providesa direction which the testing department adheres to and follows. It applies both to new projects and maintenance/support work and refers to the ability of a software to perform well in unforeseeable scenarios and to keep a relatively low defect rate.
QA Policy ensures the maximization of the strategic value inherent in every project.
Primaryobjective of Quality Assurance is that a software application:
- Meets the requirements that guides its design and development.
- Maintains the level of quality.
- Satisfies the needs of stakeholders.
QA is a joint responsibility of Test Lead/Test Manager and Tester.
Entry and Exit Criteria
Entry criteria are the minimum eligibility or the minimum set of conditions that should be met in order to start the testing work.
Exit criteria are the minimum eligibility or the set of conditions that should be met in order to close a particular project phase.
Quality Assurance Verification & Validation
Verification refers to the set of activities performed in order to ensure that the software we are building correctly performs a specific function. In other words, it answers the question “Are we building the product right?”
Evaluation items include Test Plans, Test Scenarios, and Test Cases. Activities under verification could be Peer Reviews, Walkthroughs & Inspections.
Validation refers to the set of activities performed to ensure that the product which we have built complies with the customer requirement. In other words, it answers the question “Are we building the right product?”
Evaluation items include actual working product/application/software. Activities under validation could be Functional Testing, Non Functional Testing, and System Testing & UAT Testing.