Online Process Main Page How to: Create a Bug
DescriptionAs bugs are detected in the software product, they must be documented as quickly as possible so that developers can resolve them. Before opening a bug work item, you should query existing bugs to be sure the bug you discovered is not already reported. Procedures: - On the Visual Studio Team menu, click Team Explorer.
- In Team Explorer, expand your team project folder.
- Right-click the Work Items node, and choose Add Work Item, Bug.
- Complete the fields in the bug work item.
- Title - Enter a title that is complete, succinct, and thorough so that anyone querying titles can list a feature or element and easily find this bug. Your team may have naming conventions for bugs to facilitate efficient queries.
- Area - Select the appropriate node in the project hierarchy that represents the feature area or team area where the bug was found.
- Summary - Describe the bug and provide steps to reproduce the bug.
- Priority - Priority 1 is a showstopper and must be fixed as soon as possible. Priority 2 is an important bug that does not need to be fixed immediately but must be fixed before release. Priority 3 is an optional bug that may or may not be fixed depending on resources, time, and risk.
- Links - Provide additional links such as screen shots or email conversations as related to the bug.
- Test Name, ID, and Path - If the bug is the result of a failed automated test, include the test information in these fields.
- Found in Build - Indicates which build the bug was discovered in.
- Assigned To - Identifies the current owner of the bug work item.
- On the File menu, choose Save New Bug.
|
Last modified at 1/17/2008 11:18 PM by Administrator
|
|