With TFS and Visual Studio

Angela Dugan

ALM Practice Manager

Polaris Solutions

Angela Dugan

User

Interface

Services

Business Processes

Business Rules and Logic

Service integrations

Data access

Identity

Data

Automated testingUnit testingIntegration testingPerformance testingLoad testing

Manual testingUser testingAd-hoc exploratory testing Planned manual testing

Automated testingKeyword testingUI automation testingPerformance testing

Continuous integrationsBuild | Deploy | Test

Dev

SIT

UAT

Stress

Prod

Testing toolboxRole tailored tools

Lab management automation

UI regression test needs grow over time

Manual UI testing impacts the delivery cycle times

Automated UI tests are brittle, time-consuming to maintain

Record and automate UI tests

Robustly instrument UI tests to reduce maintenance overhead

Associate UI tests with a scheduled build

Test more functionality in less time

Reduce or eliminate repetitive manual testing

Reduce cycle time when delivering new features

Generate your Coded UI test from

an existing recording, or record a

new test case on the fly

Convert the test case to code

for enhanced flexibility

CodedUI tests interact

directly with your app’s UI

Tests can be run and monitored

on the local machine, or further

automated on a virtual machine

Cross-browser testing

support allows automated

testing on multiple browsers

Coded UI tests run as part of your

unit testing suite, enabling

developers to detect defects early

Even if the look & feel changes, the

automated test still executes properly

Coded UI tests are part of source

control for maximum visibility

Preferred partner solution : FrogLogic

Import and run Squish GUI

tests directly in Visual

Studio and view results

Push Squish tests into TFS

Associate Squish tests

with MTM Test Cases

Preferred partner solution : LogiGear

Keyword-driven authoring

platform using familiar tools

Fully integrated,

multi-platform testing

Library of preprogrammed

reusable actions

•

•

•

Incident management tools and workflows to integrate operations and development teams in reducing MTTR

Reduction of MTTR

• SCOM and TFS integrated workflows to manage incidents from occurrence to resolution

• One click “Assign to Engineering” from SCOM

• Collection of actionable diagnostics in production for development troubleshooting (IntelliTrace)

Testing the User Interface with Automated UI Tests: http://msdn.microsoft.com/en-us/library/dd286726%28v=vs.100%29.aspx

CodedUI Testing Walkthroughs: http://msdn.microsoft.com/en-us/library/dd286726.aspx

CodedUI Best Practices: http://msdn.microsoft.com/en-us/library/dd380782.aspx

System Testing with Visual Studio: http://msdn.microsoft.com/en-us/library/jj620889.aspx

Mark each step as pass/fail when recording manual tests

Carefully consider which test cases make sense for automation, and when

Use the Automation Status field of test cases to identify candidates for automation

Use the Coded UI Test Builder whenever possible

Do not modify UIMap.designer.cs as it may be overwritten

Create your test as a sequence of methods

Create a new test method for each new page, form, or dialog

When you create a method, use a meaningful name

Try to limit each method to fewer than 10 actions

Create each assertion using the Coded UI Test Builder

If the UI changes, re-record the test or assertion methods

Test -> Windows -> Test View -> Properties

Select CSV, XML, or SQL

this.UIMap.SimpleTestParams.UIMyTextboxEditText = TestContext.DataRow[“col_name"].ToString();

Databinding to test parameters happens automatically when converting from manual test cases

Searchingused to look for all possible controls

Filteringused to narrow that list exactly one match

X, Yonly used to guide where the clicks happen within a control Mouse.Click(uIGOButton,

new Point(19, 18));

ULTIMATE

Premium

Professional

Test

Professional

Team Explorer Everywhere

SharePoint

Office

Web Access