Module 2: Complete a story
In this module, you complete a story, and then delivers and test the story.
Learning objectives
After completing the lessons in this module, you will understand these concepts and tasks:- All tasks are linked to the story.
- Testers find completed stories by using work item queries and tracking work items in builds.
- Testers can monitor builds from their dashboards.
- Defects are submitted and automated links are created.
- Testers or developers verify that a story is done.
Time required
This module takes approximately 60 minutes to complete.- Lesson 2.1: Create test scripts
In this lesson, you complete test cases, test scripts, and test execution records to prepare for a build. - Lesson 2.2: Develop a story
In this lesson, you complete the development work for the story. You review the requirement, and then implement, build, test, and deliver changes. - Lesson 2.3: Submit a build request
In this lesson, you submit a build request that includes all changes that the team delivered. A build is the bridge between development and testing. A build generates feedback for the development team. The team delivers changes that trigger builds and the unit tests provide the feedback on development progress. Widgets, such as Build Health and Frequent Test Regressions, illustrate the relationships between builds, development, and testing. - Lesson 2.4: Test for defects
In this lesson, you monitor the status of a story to determine when it is ready for testing. After completing a test case, you submit a defect. You also associate a defect with a build result. - Lesson 2.5: Fix a defect
In this lesson, a team lead triages a defect, a developer creates a fix and delivers changes, and a tester verifies the fix. - Lesson 2.6: Confirm that the story is done
In this lesson, you confirm that the story is done.