Академический Документы
Профессиональный Документы
Культура Документы
Copyright Intertech, Inc. 2009 www.Intertech.com 800-866-9884 Slide 1 Month Date, 2006 All Rights Reserved
Test planning with Microsoft Test and Lab Manager Test Impact Analysis Coded UI testing Historical Debugger
9/18/2009
9/18/2009
9/18/2009
9/18/2009
9/18/2009
Context
Team Project Test settings (manual and automated) Configurations (hw/SW) Build
9/18/2009
9/18/2009
Plan
Suite (User Story/Use Case)
Group of test cases
Steps
9/18/2009
9/18/2009
Plan
Suite (User Story/Use Case)
Group of test cases
Steps
10
9/18/2009
11
9/18/2009
12
9/18/2009
13
9/18/2009
14
9/18/2009
Queue Build Make sure Test Impact Collector set in test settings file Run tests ( this collects the test impact data) Change the code Run new build Test manager Assign the new build Test Manager - Track/Recommended tasks http://blogs.msdn.com/densto/archive/2009/06/29/testimpact-walk-through.aspx
15
9/18/2009
16
9/18/2009
17
9/18/2009
The engine supports a wide range of platforms out-of-the box covering thick client applications built with .Net technologies to latest web applications Support for Windows Internet Explorer 7.0 and Windows Internet Explorer 8.0
Support for Win-forms Controls for Microsoft .Net framework 2.0, 3.5 SP1 and 4.0 Windows Presentation Framework (WPF) for .Net framework 3.5 SP1 and 4.0 Custom Controls
Applications written in ASP.Net, php, jsp, asp, Ajax, SharePoint and web 2.0 applications are supported. The web plug-in uses The IEDOM for identifying properties of the controls and playing back the actions. For Win-forms applications, the plug-in uses windows accessibility technology Microsoft Active Accessibility (MSAA) to identify Control properties and playback actions.
For WPF applications, the plug-in uses the UI Automation (UIA) accessibility framework in Windows to identify Control properties and playback actions. Since we rely on windows accessibility technologies, controls that follow accessibility guidelines are also supported. We are also working with partners to enable support for some popular custom controls shipped by third party vendors. Additionally, vendors can used our extensibility APIs to add improved support for their custom controls. We are currently working on adding Firefox support. It will not be available in the box at RTM but we are actively working on making it available as add-on shortly afterwards. Monitoring tools
18
9/18/2009
Identify the test environment. Identify performance acceptance criteria. Plan and design tests. Configure the test environment. Implement the test design. Execute the tests. Analyze the results, report, retest.
AKA Functional UI testing Like Webtest Works at the DOM layer in the broser If you rename controls VS may still be able to find it based on relative position Tip: Add (TestContext testContext,UIMap ui) to the method signature to allow asserts to be performed in the recorded methods. Tip: Add which method failed to the assertion Assert.AreEqual("50", ui.UIWpfWindow.UITxtSquaredEdit.Text,"square 7 test"); Tip: Test view add data source (testcontext.datarow)
19
9/18/2009
Historical Debugger collects information for selected diagnostic events only. Events are configurable (hopefully in beta 2)
Exception Debugger (start, stop, step, break) .Net Events
Local variables NOT captured Somewhere between windbg and the existin gdebugger
20
9/18/2009
21
9/18/2009
22
9/18/2009
How to enable Test Case Management , Agile Planning Workbooks, Branch Visualization, Lab Management
sample script is designed to work if the following are true: You are using the Beta1 (English) version of Team Foundation Server 2010 Your team project was created with the English language version of MSF for Agile Software Development - v4.2 process template before you upgraded your Team Foundation Server No modifications have been made to the work item type definitions on your team project before or after the upgrade You are running the script on an English operating system You need to either modify the sample script, or create your own if: Your team project was created with a process template other than MSF for Agile Software Development v4.2 (English) You have made modifications to the out of box work item type definitions on your team project Your team project already has an existing Test Case work item type You want to use the existing Repro Steps field on your Bug work item type You are using a non-English Team Foundation Server
http://blogs.msdn.com/ratnaditya/archive/2009/06/01/runni ng-automated-tests-in-manual-test-and-lab-manager-vsts2010.aspx
http://msdn.microsoft.com/enus/library/dd264963(VS.100).aspx http://msdn.microsoft.com/enus/library/dd264915(VS.100).aspx
23
9/18/2009
Copyright Intertech, Inc. 2009 www.Intertech.com 800-866-9884 Slide 47 Month Date, 2006 All Rights Reserved
24