8.3.1. Activity Description

• Test Based on sprint backlog and story complexity

In test planning, testers should develop their testing strategies based on the sprint backlog and the complexity of the stories. This means that before any testing begins, the team must understand what stories they need to test, what the requirements are, and how complicated the tasks may be. This ensures that they can allocate resources and time effectively to address the needs of each story in the sprint.

Imagine planning a road trip. Before you start, you look at the route (sprint backlog) and consider the distance and terrain (story complexity). You decide how much fuel (resources) you need and which car (start testing) is best suited for the journey based on these factors.

• Test Case Functional + boundary + negative test cases

During the design of test cases, QA must create a mixture of functional tests, boundary tests, and negative tests. Functional tests check if the software behaves as expected under normal circumstances. Boundary tests examine the limits of the input domain, and negative tests ensure that the software handles incorrect inputs gracefully. This diverse testing strategy ensures robust software by covering various scenarios.

Think of a vending machine. A functional test would check whether it dispenses the correct drink for the right amount of money (functions), a boundary test would check what happens if you insert just one cent too little (boundaries), and a negative test would involve trying to press buttons that do not exist to see if the machine crashes (negative scenarios).

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

Testing should begin as soon as a user story is deemed ready. This 'shift-left' approach moves testing earlier in the development process, allowing for earlier detection and resolution of issues. Starting testing early means that any problems can be identified before they propagate into later stages of development, leading to more efficient workflows and less rework.

Consider a student studying for an exam. If they start reviewing their material the week before (early testing), they can detect and address misunderstandings. However, if they wait until the night before (late testing), they may have many topics to clarify and limited time to fix gaps in their knowledge.

• Bug Log in real-time with clear reproduction steps

When defects are found, they should be logged in real-time, meaning that as soon as a bug is identified during testing, it is documented immediately. This report must include clear reproduction steps, allowing developers to replicate the issue easily. Clear communication regarding bugs is essential for effective resolution and helps to ensure high-quality software.

Think of it as the customer service process in a restaurant. If a diner finds a hair in their food, they should report it immediately (real-time logging) and explain exactly where they found it and what the dish was (clear reproduction steps). This allows the restaurant staff to respond quickly and address the issue effectively.

• Regression Use automation or fast manual passes for impacted areas

Regression testing involves re-running previous tests to ensure that new code changes haven't introduced new bugs elsewhere in the software. Automation can be utilized for efficient regression testing, especially for testing impacted areas, allowing testers to quickly validate that existing functionalities still work as designed.

Imagine you have a carefully stacked set of boxes in a warehouse. If you add a new box on top (new code change), you need to check if any of the boxes below have shifted or fallen (introduced bugs). Using an automated system to monitor the stability of the stack can help ensure everything remains intact.

• Test Update RTM, test summary, or status dashboard

In the closure phase of testing, updates need to be made to the Requirements Traceability Matrix (RTM), test summaries, and status dashboards. This helps track what testing has been completed, what is still pending, and how well the project is aligning with its quality goals. Clear documentation during this phase aids continuous improvement and accountability.

Think of it like a project manager closing out a project. They review the project timeline (RTM) to see what was completed, summarize the findings for stakeholders (test summary), and update everyone involved on the status of deliverables (status dashboard). This ensures everyone is aligned on the project's outcomes.

--