QA Strategy

Goal – Provide consultant services to:

Increase quality of the product by creating and performing tests, identifying errors, and providing feedback
Ensure that Product meets Client Requirements; eliminate defects in the Product before release to customers
Embedded within the scrum team, accountable for stability, reliability and scalability of the Product

Pillars:

Role of QA in the sprint

QA team, as an integrated part of scrum team, is accountable for ensuring quality, stability, and reliability
Although not all phases may be required for all releases, the phases in green above are their responsibility
QA should strive to maximize automation, and testing pragmatically with an aim to minimize firm risk

Integration Testing: Two or more independent modules combined and tested together; conducted to verify the compliance of
system with specific functional requirements. Reveals interface, communication and data flow defects between modules
Functional Testing: Verifies functionality of the application with respect to functional requirements. A common way to conduct
functional testing is by using the black box testing
Regression Testing: Verifies that adding new features did not break the existing functionality
Security Testing: Verifies that the software is free of potential vulnerabilities, known flaws and security loopholes that might
affect the system or data. Security testing is generally conducted via penetration testing
Performance Testing: Tests the reliability, scalability, and responsiveness of the system under a given workload
Stress Testing: Involves testing beyond the normal operational capacity of the system, often to a breaking point to determine
stability and safe usage limits
User Acceptance Testing: Often performed by users who have authority to signoff on the functionality – this evaluates the entire
system against the desired requirements are met