Work items like tasks may be linked to show predecessor or successor of another task. The work item task is a child of a requirement, two requirements can be related, a test case tests a requirement. Visual Studio 2010 introduced the concept of hierarchy by which a work item is linked to another work item using a linked type. All these work items can be linked to the requirement they are helping to fulfill. Additional work items can be added if not in your process template like Review, Issue, Change Request to name just a few. There are different work item types depending on the process template you are using, however all contain the following: T ask, Test Case, Shared Step, Bug. In Visual Studio other work items are used to identify work that needs to be done to a requirement before it can be deemed done.
The ability to trace a requirements state and/or status at any time during a project.įirst step in making requirements traceable.
MICROSOFT VISUAL STUDIO 2010 MSDN LIBRARY VERIFICATION
For this blog I am using the term requirement.Ĭontinuous knowledge of the life of a requirement from conception to creation to design to development to verification to implementation and change. Depending on what process you are using in TFS your stakeholders needs are documented in a work item called one of the following: requirements, user stories, use cases or backlog items. Team Foundation Server (TFS) and Visual Studio(VS) excels when it comes to requirements traceability. Set that option to keep your test results, unless you don’t want them! Make sure your teams understands what happens when deleting completedīuilds. There is an option that can be set to stop the deletion of your Test Setup and maintenance deleting could be deleting Test Results? Nothing wrong with that however is the person responsible for the “Build” You can also configure the retention policy and set auto deletion rules Symbols: The debugging symbols published to a.The specific file versions used by the build process. Label: The version control marker associated with.Test Results: Results of any automated testsĮxecuted during the build process or results of any test published against this.Drop: File and folders output by the build and.
Items associated with that completed build are deleted. If you have the right permissions you can right-click in Build Explorer You know by default Test Results from any automated tests run against the build You know that the data deleted cannot be recovered? You know that the files and data that are part of a completed build can delete?
0 kommentar(er)
