2.3. QA Involvement in Each SDLC Phase

Review requirements for clarity, testability; identify potential gaps or risks.

In the Requirements Analysis phase, the QA team reviews the requirements provided by stakeholders to ensure that they are clear and can be tested effectively. This may involve checking whether each requirement is specific enough to be understood and implemented, as well as identifying any gaps or risks that might affect the development process later on.

Imagine a new building project. The architect needs clear blueprints to ensure everything is built correctly. Similarly, QA examines requirements like an architect ensures that the plans are detailed and feasible.

Review design documents; define test strategy; participate in test planning.

During the Design Review phase, QA looks over the technical designs of the software to ensure they align with the requirements. The QA team collaborates with developers to outline the testing strategy, determining how they will test the system and what test cases will be needed, thus preparing an actionable plan.

Think of designing a new car. Before the car is built, engineers plan the structure. Similarly, QA ensures that the design documents are sound and that testing is prepared to check if the car drives safely and efficiently.

Prepare test cases/scripts in parallel; collaborate with devs for early feedback.

As development starts, QA prepares test cases and scripts that will be used to validate the software. By collaborating with developers during this stage, they ensure that testing is aligned with the development process, providing early feedback to catch issues before they become bigger problems.

This step is like a chef preparing the ingredients while others cook. By having everything ready to go, QA can ensure that they can test the final dish as soon as it is ready, rather than waiting until the cooking is done.

Execute test cases (manual/automated); log defects; perform regression, functional tests.

In the Testing Phase, QA executes prepared test cases. This can include manual testing, where testers interact with the software, or automated testing, where scripts run tests automatically. During this process, they log any defects found and perform regression testing to ensure that new changes haven't impacted existing functionality.

Imagine a quality inspector at a factory checking products. The inspector tests various items against specifications to ensure they work as intended and marks any defects that need fixing.

Perform sanity/smoke testing in staging/production; validate configurations.

When the software is deployed, QA performs sanity or smoke tests to check if the critical functionalities are working as expected in the staging or production environment. This step is crucial to validate that the software is ready for users and that all configurations are set correctly.

Think of a pilot performing checks before takeoff. Just as a pilot ensures everything is operational before a flight, QA must ensure the software is functioning correctly in real-world conditions before users engage with it.

Verify fixes, conduct regression tests, handle change requests.

During the Maintenance Phase, QA is responsible for verifying that any fixes made to the software work correctly and do not introduce new defects. They conduct regression tests to confirm that the software remains stable after changes and address any change requests from users or stakeholders.

This phase is akin to maintaining a car after purchase. Owners might need to repair or upgrade certain parts, and during this, it’s vital to test that the car still runs properly after any changes.

--