Fixing, delivering, and building

This topic describes how to find new defects, fix them, deliver your changes, and run a build that includes your changes.

In this task, the developer fixes defects, builds and tests the changes locally, and then delivers the changes to the stream. The release engineer then runs a team build.

Before you begin

Before you begin this task, the development lead reviews all defects that testers submitted, decides which defects to address in the current iteration, and assigns those defects to developers.

Step 1: Review assigned defect

In your role as developer, find new defects that the development lead has assigned to you. Then review each defect and the related artifacts to learn details about the problem.

1. Find new defects that are assigned to you for the current iteration. You can view them in the iteration plan, in your personal or team dashboard, or in the Current Work section of your My Work view.
2. Open one of your defects and review the description. On the Links tab, navigate to the corresponding plan item or development task to learn more about the feature. Navigate to the test case to learn details of the failure. You can also navigate to the related requirement.
3. Change the state of the defect to indicate that you have started working on it.

Supporting tasks:

• Viewing work items in a plan
• Managing work items in My Work view
• Finding a dashboard
• Updating work items

Step 2: Fix and deliver changes

After you research the defect and determine a solution, you are ready to make the necessary changes and share them with the team.

1. Update the source files with the changes that are required to fix the defect.
2. Check in your changes.
3. Run a personal build that includes the files in your repository workspace.
4. Review the build result. Ensure that there are no compilation errors and that all unit tests pass.
5. Open the defect and add a comment describing the changes that you made. Change the state to Resolved.
6. Associate your change set with the defect.
7. Deliver the change set to the stream.

Supporting tasks:

• Checking in changes in the client for Eclipse IDE
• Checking in changes in the IBM® Engineering Workflow Management client for Microsoft Visual Studio IDE
• Requesting builds
• Viewing build results
• Viewing build status
• Delivering change sets

Step 3: Build

After you deliver your changes, ask the release engineer to start a team build or wait for the next scheduled build to run. After reviewing the results to ensure that all unit tests are complete with no failures, the release engineer applies a tag to the build to indicate that it is ready for system verification testing.

Supporting tasks:

• Requesting builds
• Viewing build results
• Tagging builds

Results

You have delivered a fix for a defect and built a new version of the project.

What to do next

The testing team deploys the latest build so that they can verify that the defect is fixed.