1. Acceptance Test Planning
Visual Studio 11
10/27/2017
Acceptance Test Planning
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Business challenges Solutions Business value Unclear requirements
Visual Studio 11
10/27/2017
Business challenges
Unclear requirements
Delivered software does not meet value expectations
Late-breaking changes and churn cause delivery delays
Test/QA team is siloed
Solutions
Actionable requirements management using familiar tools
Collaborative quality engagement for all roles
End-to-end traceability
Business value
Reduce cycle time from ideation to delivery
Deliver value continuously while increasing quality
Delivered software meets user and value expectations
Talk Track:
Ensuring software quality is about more than just creating a bunch of test cases. All members of the team, from business analysts to operations personnel, need to work in synch with the rest of the team to ensure delivery of a quality product. A single repository for tracking all types of work performed on the application reduces the risk of implementing the wrong functionality and enables accurate reporting across all stages of the application lifecycle, reducing cycle times and enabling your team to continuously deliver a quality product.
**Note: this was written for a different slide which has been cut – see whether any of the text can be reused**
Ensuring software quality is about more than just creating a bunch of test cases.
Requirements gathered by business analysts need to be testable by creating well-defined acceptance criteria. This enables test cases to be aligned with the acceptance criteria ensuring that testers are fully vetting the functionality that stakeholders require.
Not only business analyst and testers need to align. Developers, Operations, Project Managers, and other invested parties must be on the same page as well. A single repository for tracking all types of work performed on the application reduces the risk of implementing the wrong functionality and enables accurate reporting across all stages of the application lifecycle.
To continuously deliver quality software, test cases must be applied repeatedly as new functionality is implemented. Intelligently organized test cases allows for re-use and easy regression testing. Test impact analysis will enable testers to target the correct test cases for regression, reducing wasted manpower.
Effective test cases contain clear and measurable test steps. Often repeated test steps need to be shared between test cases to ensure consistently applied standards. Well documented verification steps enable accurate testing, and reduce the likelihood of human error.
When each stage of the application lifecycle occurs in a silo, there is no easy way to assess if the testers are testing the functionality that the stakeholders require. The need for integration requires a tool that can support all stages of the application lifecycle.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3. Requirements and bugs link directly to related test cases
Visual Studio 11
10/27/2017
Requirements and bugs link directly to related test cases
Design and align
Testable, measurable requirements are the first step. Link test cases directly to requirements to ensure maximum visibility and in- depth reporting.
Talk Track:
Managing your test plans effectively requires that Business Analysts, Developers, and Testers all be on the same page. The requirements that business analysts gather must be testable. Involving stakeholders in the process of defining Acceptance Criteria helps to scope each requirement and will serve as a series of benchmarks against which the completion of the requirement can be measured.
Requirements link directly to test cases for maximum visibility
PowerPoint Storyboards can be attached to requirements for a visual representation of acceptance criteria
Well defined acceptance criteria (both functional and non-functional) ensure everyone knows what is to be implemented, and tested
Integrated Storyboarding with PowerPoint keeps stakeholders and all team members in sync
Measurable acceptance criteria, visible to all team members, aligns with tests
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

4. Create custom shapes to re-use throughout your application.
Visual Studio 11
10/27/2017
Create custom shapes to re-use throughout your application.
Test visions, not just apps
Text documentation and specifications have their place, but they can’t reliably convey the stakeholder’s vision. To get on the same page with design, interaction, and experience, create a pre-prototype using familiar PowerPoint tools, even animations and transitions, then review directly with stakeholders.
Talk Track:
PowerPoint Storyboarding allows you to create realistic mockups, including navigation and workflow, with a familiar tool. Storyboards can be linked to work items in TFS for visibility across the entire team. Since they are just PowerPoint documents, you can send them to stakeholders or clients outside of your organization for approval and editing. There are hundreds of pre-built shapes available, with more available online in the Visual Studio Gallery, to get you started. You can even add custom shapes to increase the consistency of your UI.
Create realistic mock-ups of your UI for early approval, and attach them to work items so developers know what to build
Hundreds of pre-built shapes, from iOS to Windows Phone to navigation animations
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

5. Engage stakeholders early
Visual Studio 11
10/27/2017
Free Feedback client app guides stakeholders through the feedback process
Engage stakeholders early
When stakeholders participate, projects succeed. Pairing Storyboards with the Feedback Client allows stakeholders to review from their own computer, on their own schedule, and still ensure their voice is heard. Everyone has confidence that they’re building exactly what’s desired.
Talk Track:
Engage stakeholders with the Feedback Client to gain actionable feedback from them throughout your development process. Stakeholders don’t need any licenses or proprietary software to provide feedback. The client will guide them through your application and target their feedback on specific areas of interest. Feedback requests are backed by work items in TFS, so the entire process is transparent across your team and can be linked to new backlog items requested by the stakeholders.
Provide rich feedback, including audio/video recordings, screenshots and additional files
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

6. Storyboards, taken further
Visual Studio 11
10/27/2017
Seamless connection with Visual Studio PowerPoint Storyboarding capabilities
Define the flow of a use case with powerstory
Storyboards, taken further
Keep your Storyboards, wireframes, user stories, and test cases in sync with powerstory. powerstory enables you to animate user stories and application flow, and even create manual test cases directly from PowerPoint.
Talk Track:
Powerstory brings user stories, storyboards, wireframes, and manual test cases all under one roof. You can create user stories, diagram the flow with PowerPoint storyboards and create manual test cases based directly on the steps in your storyboard all quickly and easily from PowerPoint.
Generate detailed test steps for each unique path through the main flow and alternate flows
Export generated test cases to TFS, Word & Excel
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

7. Visual Studio 11
10/27/2017
Word
Excel
Visio
Requirements your way
Add inteGREAT SmartDocs to manage requirements documentation—any process, from agile to waterfall, startup to strict regulatory compliance— easily, using the familiar Office suite. Artifacts connect directly back to TFS for total visibility, traceability, and access by the entire team.
Talk Track:
inteGREAT and inteGREAT SmartDocs by eDev Technologies bring users, analysts, tech writers, design engineers, and developers together with clear and consistent documentation authored in familiar tools suited to each team member’s role, integrated through the Team Foundation Server 2012 and Team Foundation Service platforms.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

8. Visual Studio 11
10/27/2017
Quickly see the status of any test suite; reports and dashboards provide deeper analytics
Attach test suites to iterations to keep everyone on the same timeline
Get organized
Your list of tests will grow. That’s the idea. Test suites keep test cases organized in logical groups. Organize your test suites according to requirements, categories, or free-form to suit your team’s needs.
Talk Track:
As the number of test cases grows, performing targeted regression testing as new functionality is added becomes more and more difficult. Intelligently organized test cases, combined with Test Impact Analysis, allows your testers to spend their valuable time where it is needed most. Knowing which tests were run against which build and on which platform also becomes increasingly difficult, especially with the decreased cycle times of modern app development.
Test suites can be scoped by requirement, a specific query, or free form to organize your test cases as you need.
Suites can be attached to specific iterations, or even specific builds
Suites can be configured for a specific testing environment, making it easy to know at a glance which platforms have been tested against
Specify configurations when testing is needed in different environments
Group and classify test cases as needed to support the team’s process
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9. Visual Studio 11
10/27/2017
Add new steps manually, or quickly record repeatable test steps during exploratory testing
Scope test cases by Area and Iteration for accurate reporting
Rinse, repeat
Continuous delivery requires repeatable tests for reliable results. First, use test cases to guide implementation, ensuring that analysts, devs and testers concur. Later, if a test fails or a defect is discovered, the same test info helps the team verify and reproduce, reducing time to repair.
Test cases link to requirements and other related work items
Talk Track:
Tests that aren’t repeatable and verifiable aren’t of much use. Clear, easy to follow test steps linked to requirements and scoped to a particular build ensure that you know exactly what was tested, and against which version of your application.
Detailed test steps can be created manually, or recorded during an exploratory test session.
Test step execution can be recorded on a step-by-step basis, so the tester can focus on the verification step
Expected results captured directly on the test case
Test cases link to all other work items (bugs, product backlog items, tasks, etc.)
Detailed test steps provide clear guidance for testers (and even developers!), ensuring consistency
Expected Results make acceptance criteria measurable
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

10. Visual Studio 11
10/27/2017
View real-time status of each user story
Track active and resolved bugs by user story
Bring it all together
Accurate, real time reporting across the entire project. Team Foundation Server is the glue that holds all the pieces together. By managing your entire development process under one roof, you get easy, in depth access to the status across your entire project, not just bits and pieces.
Talk Track:
Because TFS backs your entire development process, you can eliminate reporting silos. There are no hoops to jump through to view a single report covering implementation, bugs, and builds. Everything you need is at your fingertips, in real time.
Track total percentage hours completed by user story
Test results quickly display quality status of each user story
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11. Reduce cycle time, improve quality
Visual Studio 11
10/27/2017
Reduce cycle time, improve quality
Velocity and quality can’t be either-or. Today’s competitive marketplace demands both-and. Microsoft Visual Studio 2012 provides a single integrated platform where your teams can collaborate on quality in all phases of the lifecycle: ideation and planning, development and functional testing, deployment and maintenance, and beyond.
Talk Track:
Teams often worry that reducing their deployment cycle time will reduce overall quality.  It’s a real risk, but it can be avoided if you modernize your quality management system as well. With MTM and the Visual Studio ALM solution, your quality management integrates seamlessly into your modern development platform, ensuring that velocity and quality will go hand in hand.
Additional Resources:
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

12. 10/27/ :14 PM
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.