Many friends of mine have asked to me to explain the features in VSTS Rosario edition, so i would like to explain view things about this edition version, in this version leverage the existing or previous version in the context of ALM ( Application Life cycle Management ), here are the following points below :
· Development Scheduling and Tracking
Teams will be able to communicate tasks and progess more effectively through work item tracking, including being able to create parent-child relationships between work items, identifying task dependancies, and tracking progress through readily available spreadsheets and reports.
· Requirements Test Coverage and Manual Testing
Being able to see the relationship between test cases and software requirements gives the test team an opportunity to identify missing test cases early, to identify which test cases are failing for a particular requirement, and to recognize trends in failing test cases. Running automated and manual test cases, testers can find and report bugs. Using the new manual test runner, they will be able to include more bug data than was previously available.
· Dependency Management
Developers will be able to easily identify cross-task dependancies, enabling other developers on the team to prioritize their work .
Development Scheduling and Tracking
Visual Studio Team System code name “Rosario” improves the way you schedule and manage work items and track progress. Either through integration with Microsoft Excel, or through Visual Studio Team Explorer, you can enter, edit, and track the progress of work items. With this CTP release you can link work items in a parent-child relationship, which enables you to track the progress of requirements from feature definition through to task completion.
With this release the new capabilities include:
· Improved integration with Excel
· Linking work items with parent-child relationships
· Progress tracking based on parent-child relationships
Requirements Test Coverage and Manual Testing
This CTP release enables you to view business requirements based on their existing test coverage, which enables you to identify gaps in the current test plan. Once you have identified the business requirements that are lacking test coverage, you can create test cases that link to these requirements.
The addition of a standalone manual test runner enables you to run tests outside of the IDE. In the event that you find a bug , you can record more data than was previously available. You can use the manual test runner to download a test run from a Team Foundation Server, publish test results, and open bugs with detailed data including screenshots, automatically collected system information, reproduction steps, and a video screen capture of the steps taken to find the bug.
With this release the new capabilities include:
· Test coverage queries showing requirements missing tests
· Manual test runner
- Test cases
- Run test cases stored on a Team Foundation Server
- Publish the results of a test case run
- Bugs
- File a bug
- Automatic collection of system information
- Ability to include screenshots
- Logging of reproduction steps
- Video screen capture of events triggering bug
- Dependency Management
Cross-team communication is essential to any project and the addition of the work item dependency feature is built to support this. With this CTP release, team members can now identify work items that their work items are dependant on, enabling the team to identify the priority of tasks based on these dependancies. Any team member can view a list of work items that are dependant on his assignments by running a work item query. These work item dependancies are also trackable through reports.
With this release the new capabilities include:
· Work item dependency identification
· Work item dependency tracking and reporting
Entries (RSS)