8.3. Sprint Testing Activities

QA works in parallel with developers to test stories as they are built.

In Agile methodology, Quality Assurance (QA) professionals work alongside developers throughout the development process, instead of waiting until the end to test. This means that as developers create new features (referred to as 'stories'), QA is continuously involved, testing those features in real-time. This collaborative environment promotes immediate feedback and faster resolution of issues.

Imagine a chef preparing a meal. Instead of completing the entire dish before tasting it (which might lead to problems if it’s not seasoned right), the chef tastes each ingredient as they go along. This way, they can make adjustments immediately, ensuring the final product is delicious. Similarly, in Agile, QA 'tastes' the development as it happens, ensuring quality at every step.

Activity Description Test Based on sprint backlog and story complexity.

During the planning phase of the sprint, QA determines the extent of testing needed based on the complexity of the stories in the sprint backlog. This involves assessing which features require more in-depth testing and which can be tested more simply. Proper planning ensures that all aspects of the stories are covered and that resources are allocated efficiently.

Think of planning a road trip. If you know you’re traveling through mountainous areas, you might plan for extra stops and ensure your vehicle is in top shape. Similarly, during sprint planning, QA assesses each story’s complexity to ensure adequate tests are prepared, just like planning for potential challenges on a trip.

Test Case Functional + boundary + negative test cases.

In this phase, QA designs various test cases that include functional tests (checking if features work as intended), boundary tests (testing the limits of input values), and negative tests (checking how the system reacts to invalid inputs). This diversity in testing ensures comprehensive coverage of potential scenarios that may occur.

Consider testing a new smartphone application. Functional tests would check if you can send a message, boundary tests might explore what happens when you hit character limits, and negative tests would examine how the app reacts to incorrect login attempts. Each type of test helps ensure that the application performs well under all circumstances.

Test Start as soon as a story is ready (shift-left).

Test execution in Agile occurs as soon as a story is deemed ready, a practice known as 'shift-left' testing. By starting testing early in the development process, potentially expensive and time-consuming mistakes can be caught and fixed sooner, making it easier to maintain a smooth flow of development.

Think of building a house. If you start checking the plumbing as soon as it’s installed instead of waiting until the walls are built, you can easily make corrections before it’s too late. This proactive approach, similar to shift-left testing, saves time and resources in the long run.

Bug Log in real-time with clear reproduction steps.

QA logs bugs as they are found, providing clear reproduction steps to help developers understand and fix issues efficiently. This immediate logging allows developers to address bugs quickly, preventing bottlenecks in the sprint and facilitating a more agile response to challenges.

Imagine a customer service representative logging a problem as soon as they receive a complaint. By documenting all necessary details immediately, they ensure that the technical team can resolve the issue swiftly and effectively. Similarly, QA's timely bug reporting enhances the development process.

Use automation or fast manual passes for impacted areas.

Regression testing ensures that new changes do not negatively impact existing functionality. Agile teams often use automated tests for this purpose, allowing for quick checks of previously tested features. This integration of testing ensures that updates maintain overall software integrity without slowing down the development pace.

Consider a software upgrade to a popular video game. After adding new features, developers run tests to ensure that none of the original gameplay elements were broken. Just as game developers use pre-existing tests to verify new changes, Agile teams utilize regression testing to ensure new developments do not cause issues.

Update RTM, test summary, or status dashboard.

At the end of the sprint, QA updates relevant documentation such as the Requirements Traceability Matrix (RTM), test summaries, or status dashboards to reflect the testing outcomes. This closure phase is critical for maintaining accurate records and helps teams assess their testing coverage and outcomes.

Think of finishing a project at work. You would compile your notes, highlight key points that matter to management, and ensure everything is documented correctly. Similarly, after sprint testing, QA summarizes their findings, which serves as a resource for future work and helps the team learn from past experiences.

Agile relies on frequent feedback loops to deliver quality fast.

In Agile, rapid feedback loops are essential for maintaining quality as new features are developed. Integration with Continuous Integration/Continuous Deployment (CI/CD) processes enables QA to run tests with every code push, ensuring issues are identified and resolved swiftly. Automation plays a crucial role in this process, allowing for quick repeatable tests that detect issues fast.

Consider a restaurant that serves customers rapidly. Instead of waiting for complaints to pile up, the staff continuously ask for feedback on each dish as they serve them, making adjustments as needed. This timely feedback not only helps improve the dining experience but also reduces the likelihood of serious issues. Similarly, in Agile, continuous feedback helps ensure high-quality software.

--