Creating Robust, Maintainable Coded UI Tests with Visual St - PowerPoint Presentation

388 views
Uploaded On 2016-03-04

Creating Robust, Maintainable Coded UI Tests with Visual St - PPT Presentation

Brian Keller Sr Technical Evangelist Microsoft Corporation DEV312 I work here on this and this httpbitlyThisWeekC9 I blog here httpblogsmsdncombriankel httptinyurlcomALM2010Book ID: 241431

microsoft 2012 test http 2012 microsoft http test team visual foundation server studio support tests apis supported coded testing

Link:

Copy

Embed:

<iframe width="560" height="315" src="https://www.docslides.com/embed/241431" frameborder="0" allowfullscreen></iframe>

Download Presentation from below link

Download Presentation The PPT/PDF document "Creating Robust, Maintainable Coded UI T..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.

Presentation Transcript

Slide1
Slide2

Creating Robust, Maintainable Coded UI Tests with Visual Studio 2012

Brian KellerSr. Technical EvangelistMicrosoft Corporation

DEV312Slide3

I work here…Slide4

…on this…Slide5

…and this.

http://bit.ly/ThisWeekC9

Slide6

I blog here:

http://blogs.msdn.com/briankel Slide7

http://tinyurl.com/ALM2010Book

http://tinyurl.com/TFSBookSlide8

http://tinyurl.com/ALM2012

http://

tinyurl.com/ProTFS2012Slide9

Objectives

Find more UI regression bugs by employing coded UI tests.

Build and maintain robust coded UI tests.

Create coded UI tests which result in fewer false positives.Slide10

What You’ll Need

Visual Studio

2012

Premium or Ultimate

# or VB skills

Microsoft Test Manager (optionally

)

Team Foundation Server (optionally)

Testable applicationSlide11

Test Automation Platform Support

Fully supported platform

Partial solution. Further work required in future to complete

Best efforts with known issues. Users can workaround these cases in the code. No major ongoing investment.

Currently no support but on the roadmap for future releases

Currently no support and none planned for

now. O

pportunity for partners to add

this using the

Extensibility support

Docs and samples around extensibility are

here

For latest info refer to

this article

Platform

Support

Notes

IE7/8/9– HTML/AJAX

IE9 partially supported in SP1.

Windows Forms 2.0+

.NET

Controls fully supported, working on 3

party support.

WPF 3.5+

.NET Fx Controls fully supported, working on 3rd party support.SharePoint 2007 & 2010See blog post for more info.FireFox – HTML/AJAXSupported in Feature Pack 2 for FF 3.5 & 3.6.SilverlightSupported in Feature Pack 2 for Silverlight 4, in-browser apps.Windows Win32May work with some known issues, but not officially supported.Dynamics (Ax)Partially supported – see article. Dynamics CRM web client is supported.MFCPartial support – Known issues & WorkaroundsCitrix/Terminal ServicesThe client (MTM or VS) need to be on the remote machine.Office Client AppsIE 6/Chrome/Opera/SafariOpportunity for partners to add this using the Extensibility support. Docs and samples around extensibility are here.Flash/JavaSAPSlide12

demo

Coded UI TestsSlide13

Get Used to Using Using

. It’s Useful!using

(ApplicationUnderTest.Launch(this.UIMap.LaunchAppParams.UIMyWindowsFormsAppWindowExePath,

this.UIMap.LaunchAppParams.UIMyWindowsFormsAppWindowAlternateExePath))

{

this

.UIMap.SimpleTest

();

…

}

Note: This is required in 2010 only.

In 2012, app closes when test run finishes.

Use

ApplicationUnderTest.CloseOnPlaybackCleanup

BrowserWindow.CloseOnPlaybackCleanup

o preserve between test methods.Slide14

Understand Searching and Filtering

http://tinyurl.com/SearchAndFilter

Searching is used to look for all possible controlsFiltering is used to narrow that list to exactly one matchX, Y is only used to guide where the clicks happen within a control

Mouse.Click

(

uIGOButton

new Point(

19, 18

));Slide15

Employ Databinding

Test → Windows →

Test View → Properties →Select CSV, XML, or Database.this.UIMap.SimpleTestParams.UIMyTextboxEditText = TestContext.DataRow

[“

col_name

"].

ToString

();

Note:

Databinding

to test parameters

happens

automatically

when converting from manual test cases

Note: This dialog is currently not available in Visual Studio 2012. Need to hand-edit data connection attributes.Slide16

Make Friendlier Assertions

Makes it easier to analyze test run data

Assert.AreEqual(foo, bar, "Sales tax total is wrong.");Slide17

Smile! You’re on Camera

Image

pic = this.<top_level_window>.CaptureImage();

//Or for entire desktop: Image pic =

UITestControl.Desktop.CaptureImage

();

pic.Save

(

@"c:\file.bmp"

);

TestContext.AddResultFile

(@"c:\file.bmp"

);Slide18

Enable Rich Action Logs

QTAgent32.exe.config:<system.diagnostics

> <switches> <add name="EqtTraceLevel" value="4" /> </switches> </system.diagnostics

appsettings

add key="

EnableHtmlLogger

" value="true"/>

add key="

EnableSnapshotInfo

" value="true"/>

appsettings

>Slide19

Microsoft Test Manager

→ CUIT Workflow TipsMark each step as pass/fail when recording manual tests

Carefully consider which test cases make sense for automation, and whenUse the Automation Status field of test cases to identify candidates for automationSlide20

Continue on Error

For actions that may not happen

every timePlayback.PlaybackSettings.ContinueOnError = true;

orSlide21

Multiple UI Map Files

http://tinyurl.com/MultipleUIMaps

Allows you to separate logical collections of controlsEasier to edit independentlyEasier to version controlRequires a bit more up-front effortDoesn’t play well with MTM workflowSlide22

Test API

http://

testapi.codeplex.com/Input Injection APIs Command-Line Parsing APIs

Visual

Verification APIs

Combinatorial

Variation Generation APIs

Managed

Code Fault Injection APIs

Text

String Generation APIs

Memory

Leak Detection APIs

Object

Comparison

APIs

More…Slide23

Coded UI Test Enhanced Framework

http://cuite.codeplex.com/

Simplifies CUIT codeEliminates need to maintain multiple UI mapsLogical support for tablesBuilt and supported by the communitySlide24

Making Your Applications More Testable

Use a testable application stackGive names to controls

Use naming conventions and stick with themIf you need to change the names of controls, refactor them along with your testsCarefully consider the implications of changing UI flowsEducate non-test developers on CUITsEducate manual testers on CUITsSlide25

Playback Settings

Search timeoutsSearch behaviors

Error behaviorsSee http://tinyurl.com/PlaybackSettings Slide26

Windows Automation API 3.0

If running an O/S prior to Windows 7/2008 R2, install this platform update: http://support.microsoft.com/kb/971513/

Slide27

What About Load Testing?

Coded UI tests assume they have “control” of the mouse and keyboardLoad testing can be accomplished but you need one machine (physical or virtual) per virtual user

See http://msdn.microsoft.com/en-us/library/ff468125.aspx Slide28
Slide29
Slide30

Environments

SCVMM Environment

Standard EnvironmentBuild-Deploy-Test

Snapshot / Restore

Share Bug Snapshots

Network Fencing

Party Virtualization

Physical MachinesSlide31

demo

Using Lab Managementwith Coded UI TestsSlide32

Go get started!