Work with Rol: Analyst and Rol: Developer to identify which use-case scenarios need new or additional test cases. Review the Artefacto: Iteration Plan to ensure you understand the scope of development for the current iteration.

Identify paths through the use-case scenario as unique test conditions.  Consider alternative or exception paths from both a positive and negative perspective.  Review the test ideas list for patterns of test cases that apply to the use-case scenario.

Discuss the requirement with the Rol: Stakeholder to identify other conditions of satisfaction for the requirement.

List the test cases with a unique name that identifies the condition they evaluate or their expected result.

For each test case, write a brief description with an expected result.  Ensure that a casual reader can clearly understand the difference between test cases.  Note the logical pre-conditions and post-conditions that apply to each test case. Optionally, outline steps for the test case.

Verify that test cases meet the Lista de comprobación: Test Case guidelines.

For more information on the test case, see Plantilla: Test Case.

Review each test case and note where data input or output might be required. Identify the type, quantity, and uniqueness of the required data, and add these observations to the test case. Focus on articulating the data needed and not on creating specific data.

For more information on test data selection, see Lista de comprobación: Test Case.

Walk through the test cases with the Rol: Analyst and Rol: Developer responsible for the related use-case scenario.  Ideally, the Rol: Stakeholder also participates.

Ask the participants to agree that if these test cases pass, they will consider these requirements implemented.  Elicit additional test ideas from the Rol: Analyst and the Rol: Stakeholder to ensure you understand the expected behavior of the use-case scenario.

During the walkthrough, ensure that:

• The Artefacto: Use Case and Artefacto: Supporting Requirements planned for the current iteration have test cases.
• All the participants agree with the expected results of the test cases.
• There are no other conditions of satisfaction for the requirement being tested, which indicates either a missing test case or a missing requirement.

Optionally, capture new patterns of test cases in the test ideas list (see Concepto: Test Ideas).