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 Hudda as a whole and provides 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 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.
Primary objective of Quality Assurance is that a software application:
- Meets the requirements that guide 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.
Quality Assurance Verification & ValidationVerificationrefers 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.
Validationrefers 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.