Automating UI Testing Using Visual Studio 2012 Clive G Hermann

Automating UI Testing Using Visual Studio 2012 Clive G Hermann
Module0– Introduction Automating Coded UI Testing using Microsoft Testing Tools in Visual Studio 2012 Clive G Hermann © GSAtrain

IOS Development for iPhone and iPad iOS 6
Module 1 – Introducing the Fundamentals Introductions Name Title/Function Job Responsibility Testing Experience C# Experience Expectations for the Course © GSAtrain

Module 1 – Introducing the Fundamentals Course Materials © GSAtrain

Module 1 – Introducing the Fundamentals Course Contents Overview of Automated Code UI Testing Walkthrough steps from beginning-to-end Creating Manual Tests Creating a coded UI test Using Coded UI Test Builder Automating Coded UI Test Cases Introduction to Application Lifecycle Management (ALM) Anatomy of Coded UI Tests New Visual Studio 2012 ALM Features Automating Coded UI Tests Notes: © GSAtrain

Module 1 – Introducing the Fundamentals Course Contents 2 Data Driven Coded UI Tests Anatomy of Code UI Tests Introduction to Lifecycle Management Extending Coded UI Tests and Action Recordings Testing Large Applications with Multiple UI Maps Using HTML5 Controls in Coded UI Tests Visual Studio 2012 ALM Features Upgrading Coded UI Tests from Visual Studio 2010 © GSAtrain

Module 1 – Introducing the Fundamentals Course Contents 3 Using WPF with Coded UI Tests Best Practices for Coded UI Tests Using the Coded UI Test Logs Using SharePoint with Coded UI Tests ExcelCodedUIHelper © GSAtrain

Overview of Automated Code UI Testing
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Overview of Automated Code UI Testing © GSAtrain

Reality of Automated Testing
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Reality of Automated Testing 70% of all Testing is manual © GSAtrain

Module 1 – Introducing the Fundamentals Code UI Tsting Replacing a Manual User Interface Test With a Automated User Interface Test To Allow: Replication Consistency Regression Testing For: Multiple Environments Multiple Versions © GSAtrain

1) Overview of Automated Code UI Testing
Automating UI Testing Using Visual Studio 2012 Module 1 – Introducing the Fundamentals 1) Overview of Automated Code UI Testing UI Testing Functional Testing Controls User Interface Whole Application The earlier we catch a “bug” or potential problem the less it costs! Image Manpower © GSAtrain

Module 1 – Introducing the Fundamentals IT Has a Problem © GSAtrain

Module 1 – Introducing the Fundamentals Test Early and Often Catching defects as early as possible is the least expensive way to ensure software quality. Kent Beck and Cynthia Andres wrote "Here is the dilemma in software development: defects are expensive, but eliminating defects is also expensive”. “However, most defects end up costing more than it would have cost to prevent them." © GSAtrain

The Testing Trends Forwards
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals The Testing Trends Forwards Test-Driven Development Design the Test Then Write the Code © GSAtrain

The Testing Trends Backwards - Circular
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals The Testing Trends Backwards - Circular Linking Help-Desk Test Story Board Task Unit Programmer © GSAtrain

The Ultimate Goal of Software Testing
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals The Ultimate Goal of Software Testing To find the bugs before your users do! UI Testing is END USER TESTING OR TOTAL SYSTEM TESTING OR INFRASTRUCTURE TESTING © GSAtrain

Module 1 – Introducing the Fundamentals Manual to Coded UI © GSAtrain

Testers Multiple Roles
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Testers Multiple Roles Guarantee SOFTWARE QUALITY Regression Test each Version or build Test all Environments Provide Developers with all the information required: To REPRODUCE THE “BUG” Trace the steps to get the BUG Screen shots, IntelliTrace, Logs and Stack Traces NO-REPRO must be ELIMINATED © GSAtrain

Tiers of Software Testing
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Tiers of Software Testing Clear Separation of Functions Clear Definition of Communication and Collaboration TEAM of Software Quality © GSAtrain

2)Walkthrough steps from beginning-to-end
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals 2)Walkthrough steps from beginning-to-end © GSAtrain

2)Walkthrough steps from beginning-to-end
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals 2)Walkthrough steps from beginning-to-end Lesson 1 Manual Testing Using Microsoft Test Manger to create and manage Test Plans Running Test Cases and Publishing Results Conducting Exploratory Testing Fast Forward for Manual Testing Lesson 2 Coded User Interface Testing Automated Functional Tests – Using CUIT Create a CUIT from Scratch Create a CUIT from action recording Making CUIT more Robust and Flexible © GSAtrain

A manual testing process
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals A manual testing process © GSAtrain

Building an App For Manual Testing
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Building an App For Manual Testing Demo of Simple Calculator © GSAtrain

Automating the Calculator
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Automating the Calculator Demo © GSAtrain

Module 1 – Introducing the Fundamentals Adding Data Demo © GSAtrain

Module 1 – Introducing the Fundamentals Introducing an Error Demo © GSAtrain

Module 1 – Introducing the Fundamentals Lab 1 The Calculator © GSAtrain

Module 1 – Introducing the Fundamentals 3 Creating Manual Tests © GSAtrain

Visual Studio 2012 Supported Test Types
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Visual Studio 2012 Supported Test Types © GSAtrain

Microsoft Test Manager
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Microsoft Test Manager Provides a single environment to author and manage Tests © GSAtrain

Module 1 – Introducing the Fundamentals © GSAtrain

Quick Start Guide for Manual Testing using Microsoft Test Manager
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Quick Start Guide for Manual Testing using Microsoft Test Manager © GSAtrain

Easily reproducing issues through manual testing
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Easily reproducing issues through manual testing Introducing Managed Exploratory Testing The 5 Minute “elevator” Video Premium-and-Ultimate-Overview/Visual-Studio-Ultimate Easily-reproducing-issues-through-manual-testing © GSAtrain

6 Data DrivenTests

6 Data Driven Tests Any Files Used in The Tests
Example XML to load Variable and Expected Data Could be: SQL Business Connectivity Services SharePoint Lists SQL Reports Excel / PowerPivot SSAS

DEMO and Lab

4) Creating a coded UI test Using Coded UI Test Builder
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals 4) Creating a coded UI test Using Coded UI Test Builder © GSAtrain

4) Creating a coded UI test Using Coded UI Test Builder
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals 4) Creating a coded UI test Using Coded UI Test Builder Test Types Microsoft Test Manager Exploratory Testing Easily reproducing issues through manual testing © GSAtrain

Module 1 – Introducing the Fundamentals Authoring a TEST case Demo Lab © GSAtrain

Microsoft Test Manager
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Microsoft Test Manager The first time you run MTM it will prompt Add Team Foundation Manager “If you don’t know the Name contact your administrator” It might require “ServerName:Port Number” © GSAtrain

Module 1 – Introducing the Fundamentals TFS and MTM © GSAtrain

Connecting Microsoft Test Manager to TFS
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Connecting Microsoft Test Manager to TFS MTM is always connected to TFS © GSAtrain

Module 1 – Introducing the Fundamentals Story Boards A user story can be stated as simply as As an Employee I want to have an efficient way to manage my expenses. The conversation around this statement between the product owner and the development team can raise questions such as: Who can submit expense reports? What states can an expense report be in? When is it possible to change or remove an expense report? What data is required in an expense report to register it correctly? Where are the expense reports stored? For how long? © GSAtrain

Adding Detail to User Stories
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Adding Detail to User Stories An expense report has the following state model: New when created Pending after submitted for approval Approved Rejected © GSAtrain

Story Boards are Vital to Testing
Allows the Tester to Verify what should happen If this does not Happen See the Tasks that were assigned to this requirement See the Programmers assigned to Each Task Notify the Developer(s) Provide the necessary info to avoid “NO REPRO” Add this Test to the “Suite”

Module 1 – Introducing the Fundamentals Test Plan Properties Figure Test plan properties © GSAtrain

Module 1 – Introducing the Fundamentals Test Suites Static suite: The content of this suite is manually added test cases. Query-based suite: A query-based suite lists all test cases matching a given work item filter. Requirements-based suite: This suite shows the test cases associated with a selected TFS requirement. © GSAtrain

Module 1 – Introducing the Fundamentals Static suite: The content of this suite is manually added test cases. Query-based suite: A query-based suite lists all test cases matching a given work item filter. Requirements-based suite: This suite shows the test cases associated with a selected TFS requirement. © GSAtrain

Configuring Test Settings
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Configuring Test Settings Establish Environments Diagnostic Connectors Best Practice Work with Development Teams The Developers need to have the same tools to view the test data you collected for them Microsoft released a “Test Attachment Cleaner” available at “Aka.ms./TFPowerTools” © GSAtrain

Module 1 – Introducing the Fundamentals Using Builds Scout Installing Software and running some initial tests After the SCOUT is successful it can become a “template for other Testers” There is an available builds DROPDOWN Click “ASSIGN TO PLAN” to add a new build to a plan © GSAtrain

Analyzing Impacted Tests
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Analyzing Impacted Tests Quickly identify tests that need to be run based on changes to code Can Run in the background “Track” menu => Recommended Tests Does not recognize “DATA” changes Does not recognize other library changes Does not recognize other Application changes Best Practice - Periodicaly run all Tests © GSAtrain

Defining Multiple Test Configurations
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Defining Multiple Test Configurations Environments may differ: IE 8,9,10 Ipad Horizontal/Vertical BYOD HTML5 ETC. © GSAtrain

Test Cases are organized in to Suites
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Test Cases are organized in to Suites Requirements-Based test suite Query-Based test suite Static Test Suite Status of tests in TEST SUITE In planning In Progress Completed © GSAtrain

Module 1 – Introducing the Fundamentals Types of Tests 1 – Unit and Component Tests 2 – Functional Tests 3 – Exploratory Testing 4 – Capability Testing © GSAtrain

Unit and Component Tests
Unit and component tests are automated tests written to help the team develop software effectively. With good suites of unit and component level tests we have the safety net that helps us develop software incrementally in short iterations without breaking existing functionality. Invaluable when refactoring code. With good test coverage a developer should feel confident to make a change without knowing all about every dependency. The tests should tell us if we did wrong

Functional Tests Functional Tests
Functional tests are mainly our traditional scripted system tests in different flavors. It is hard to avoid running these tests manually at first, but we should try to find ways to automate them as we learn more about our product and how it needs to be tested. Many functional tests can be automated and then we can focus on early testing for the manual tester

Exploratory Testing Exploratory testing is a form of software testing in which the individual tester can design and run tests in a freer form. Instead of following detailed test scripts, the tester explores the system under tests based on the user stories As the tester learns how the system behaves the tester can optimize the testing work and focus more on testing than documenting the test process.

Capability Testing Lastly we have the capability tests.
These tests are run against the behavior of the system; we test non-functional requirements Performance Security These tests are generally automated and run using special purpose tools, such as load test frameworks and security analyzers.

Exploratory Testing We should leave this category of tests as manual tests. The focus should be to catch bugs that would fall through the net of automated tests. A key motivation for automated testing is to let do more of exploratory and usability testing because these tests validate how the end-user feels when using the product.

Module 1 – Introducing the Fundamentals Testing Pyramid © GSAtrain

Module 1 – Introducing the Fundamentals Testing Structures © GSAtrain

Module 1 – Introducing the Fundamentals Using Shared Steps Demo LAB © GSAtrain

Assigning Configurations
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Assigning Configurations Demo © GSAtrain

7) Anatomy of Coded UI Tests
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals 7) Anatomy of Coded UI Tests When you create a Coded UI Test, the Coded UI Test Builder creates a map of the user interface under test, and also the test methods, parameters, and assertions for all tests. It also creates a class file for each test © GSAtrain

Evolution of Decoupling
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Evolution of Decoupling In-Line Programs Sub-Routines Functions Time Sharing On-Line Terminals Client Sever 3 Tier Architecture Thin Client MVC SOA © GSAtrain

De Coupling of Software Testing
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals De Coupling of Software Testing Developers – View Individual Units of Code Administrators Build Environments and Versions Testers Test Complete Applications © GSAtrain

Module 1 – Introducing the Fundamentals Primary Drivers of SOA Inability of TESTERS to test BlackBox Code 10,000 lines of code could result in 1 Million Routes Impossible to Test Interface – Contract testing – is practical CLOUD increases the environment exponentially Interfaces are constant © GSAtrain

Microsoft Commitment to the Cloud
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Microsoft Commitment to the Cloud Microsoft Windows 2012 Windows 8 Office 2013 Office365 SQL 2012 SharePoint 2012 LINQ 2012 are all Cloud – SOA Oriented. © GSAtrain

Module 1 – Introducing the Fundamentals Azure Services The platform includes five services: Live Services for communication and collaboration services SQL Azure (formerly SQL Services) for data-storage services AppFabric (formerly .NET Services) for cloud-computing services SharePoint Services for web-content-management and document- management services Dynamics CRM Services for customer-relationship-management services © GSAtrain

Testing is Moving to the CLOUD
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Testing is Moving to the CLOUD Microsoft TFS is now Cloud Based © GSAtrain

Benefits of TFS in the Cloud
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Benefits of TFS in the Cloud Collaboration is the Key to TFS Developers Testers – Creating Reproducible Automated Tests Administrators – Builders of (Virtual Machines and Versions) Using TFS in the cloud can help us enhance collaboration It can also enhance collaboration in an organization with geographically spread locations. © GSAtrain

Concerns with TFS in the Cloud
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Concerns with TFS in the Cloud With TFS in the cloud is that we can neither add our own process template nor make adjustments to the existing templates. © GSAtrain

Service Oriented Architecture
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Service Oriented Architecture Interface Testing Viewing Objects from the outside Leads to Unit Testing Test-Driven Design © GSAtrain

Module 1 – Introducing the Fundamentals IT has a Problem! ACCELERATING RATE OF CHANGE © GSAtrain

Reasons for SOA Rapid Adoption
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Reasons for SOA Rapid Adoption © GSAtrain

What is the Relationship Between Cloud and SOA
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals What is the Relationship Between Cloud and SOA The short answer is: Cloud is an initial application of SOA to infrastructure --its setup, configuration, monitoring , management , with the essential elements of metering and billing added to satisfy the goal of a charge model of e.g., pay-as-you-go -- the specific requirements for XaaS: resource pooling and virtualization , elasticity and multi-tenancy, dynamic configuration and provisioning Cloud paradigm leverages SOA to deliver a charge-based model for non-business specific services; -- infrastructure/hardware -- software --platform s=15&sortby=0&lang=en © GSAtrain

Module 1 – Introducing the Fundamentals SIMM © GSAtrain

Module 1 – Introducing the Fundamentals DOD is Insisting on SOA Vulnerabilities Security Testing © GSAtrain

Definition of a Service
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Definition of a Service Discoverable Self-Describing Composable Loose Coupling Governed by Policy Independent of Location, Language and Protocol © GSAtrain

Module 1 – Introducing the Fundamentals SOA Maturity Model © GSAtrain

Module 1 – Introducing the Fundamentals IT Benefits Of SOA © GSAtrain

Module 1 – Introducing the Fundamentals SOA © GSAtrain

Tiers of Software Testing
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Tiers of Software Testing Clear Separation of Functions Clear Definition of Communication and Collaboration TEAM of Software Quality © GSAtrain

The interfaces may Change
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals The interfaces may Change The number of versions will increase The number of Environments will increase The need for Automation and Regression Testing will increase UI Testing will still be “Complete Application” or “END- USER Testing” © GSAtrain

The UNFORTUNATE REALITY
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals The UNFORTUNATE REALITY 70% of all Application Testing is MANUAL © GSAtrain

Module 1 – Introducing the Fundamentals Visual Studio 2012 Visual Studio Ultimate, Visual Studio Premium and Test Professional include a Microsoft Test Manager to help you define and manage your testing effort by using test plans. You create a test plan and add any test suites, test cases, or configurations that you need © GSAtrain

Visual Studio 2010 to 2012 Completely Restructured Software Testing
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Visual Studio 2010 to 2012 Completely Restructured Software Testing In 2012 Visual Studio Improves: Integration between testing and the rest of the Software Development lifecycle Example – Better handoff from tester to developer Less NO REPRO Improved build-deploy-test workflow Improved Virtualization © GSAtrain

Types of Test Supported by VS 2012
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Types of Test Supported by VS 2012 Manual Tests Coded UI Tests Unit Tests Web Performance Tests Load Tests Generic Tests Ordered Tests © GSAtrain

Module 1 – Introducing the Fundamentals Manual Tests Require a Human to Interact with an application Verify some expected result Report on the success of the test © GSAtrain

Module 1 – Introducing the Fundamentals Coded UI Tests Provides the Capability to author tests that automatically interact with user interface Verify Results File Bug Report It can be run Frequently without human intervention Typically more expensive to author and maintain than manual test © GSAtrain

Module 1 – Introducing the Fundamentals Unit Tests Used by Programmers for Programmers Quickly becoming the standard practice A vital part of Test-Driven Development Generally focus on a lower level than other Testing Ideally a unit is the smallest atomic part - One method of One object Test written before the object It will initially fail Correct Re-test Refactor Repeat Essential component of Regression Testing © GSAtrain

Module 1 – Introducing the Fundamentals Web Performance Tests Verify that the web site is behaving as expected Add load to see if the application is still capable of Scaling © GSAtrain

Module 1 – Introducing the Fundamentals Load Tests Tests that Application Scales and Performs as Necessary © GSAtrain

Module 1 – Introducing the Fundamentals Generic Tests Calling external testing systems Results can be automatically parsed to determine success Could be simple console application to XML document exported from LOB © GSAtrain

Module 1 – Introducing the Fundamentals Ordered Tests Container for other tests Specific order of tests Some run more than once © GSAtrain

Diagnostic Data Adapters
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Diagnostic Data Adapters The Key challenge of Testers Provide Developers with sufficient information to reproduce the problem Most Bugs result in No Repro “It Works on my machine” © GSAtrain

Diagnostic Data Adapters
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Diagnostic Data Adapters A Diagnostic Data Collector is responsible for collecting data about the machine under test Action Log ASP.NET Profiler Code Coverage IntelliTrace Event Log System Information Test Impact Video Recorder Network Emulation © GSAtrain

Module 1 – Introducing the Fundamentals Developers view Test-Driven Development Unit Testing © GSAtrain

Test-driven development (TDD) WikiPedia
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Test-driven development (TDD) WikiPedia Is a software development process that relies on the repetition of a very short development cycle: First the developer writes an (initially failing) automated test case That defines a desired improvement or new function Then produces the minimum amount of code to pass that test Refactors the new code to acceptable standards © GSAtrain

Module 1 – Introducing the Fundamentals Tester’s View Not Unit Testing Not Integration Testing Not Regression Testing Whole Application Testing © GSAtrain

Requirements-Driven Testing
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Requirements-Driven Testing When requirements or user stories, or features are ready to be tested, you can run your tests for each configuration that you specified UI – User Interface Testing Usability - Testing © GSAtrain

Module 1 – Introducing the Fundamentals Test Runner: The Test Runner from MTM can create action recordings from a manual test. The action recording can later be used to play back the test session in MTM or to generate a Coded UI test from the recorded steps. Coded UI Test: The implementation of the actual test written in C# or VB.NET. The Coded UI Test is either generated by the Coded UI Test builder code generator or coded directly against the Coded UI Test API. Test Recorder: Records actions from a test session, which then can be used by the Test Runner to automate a generated test or by the coded enerator to create a Coded UI test. Coded UI Test API: The Coded UI Test API can be used to create UI tests which are more tightly connected to the UI elements Technology Managers. These are the core components responsible for mapping UI elements to the underlying technology (i.e. web browser or a rich client). We can implement custom plug-ins to support platforms which the native plug-ins does not support. © GSAtrain

Managing Automated Tests
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Managing Automated Tests These tests are critical to project success The number keeps growing Regression testing is vital Sometimes hundreds or even thousand of tests © GSAtrain

Module 1 – Introducing the Fundamentals Supported Platforms As we can see from the architecture overview, the Coded UI tests require support from the platform being tested. For Visual Studio the following platforms are supported for Coded UI tests as well as action recordings: •Internet Explorer 8, 9, 10. •Windows Forms 2.0 and later •WPF 3.5 and later •Windows Win32 (not officially supported but may work) •MFC (partially) •SharePoint (partially) •Dynamics CRM •Citrix/Terminal Services (partially) •PowerBuilder (partially) © GSAtrain

Module 1 – Introducing the Fundamentals A common requirement of automated tests is to be able to run the test a number of times with different parameters. In Chapter 16 we looked at how we can work with data-driven test in details. The same techniques are valid for coded UI tests as well except that the data source for a UI test often points to the data set managed in the associated test case. Using the test case to manage test data for the automated test is nice because then the tester can update the data directly from inside MTM. © GSAtrain

Module 1 – Introducing the Fundamentals Coded UI tests are probably the ideal type of test for regression testing because they give us the opportunity to automatically test the system just like a real user would. But there are a number of issues that make UI tests difficult as a general purpose solution for automation solution, including •Requires a UI. •Requires a desktop session to run. •UI tests are more complex to design and maintain. •Difficult to scale. To work around these challenges we generally recommend considering “under-the-UI” tests as a complement to the UI tests. These tests could be written against the APIs in the system or against the controller layer in an MVC style of application. © GSAtrain

Module 1 – Introducing the Fundamentals Another option for running tests from the command-line is to use the Test Case Management command-line tool, TCM.exe. This tool is installed under C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\TCM.exe There are several options for us to start a test run, for instance: •Run all tests in a test suite. Locate the Suite Id from the test suite in MTM. tcm run /create /title:"UI Test Run" /planid:5 /suiteid:11 /configid:2 /collection: /teamproject:"Expense Reporting" You can use tcm.exe to figure out the Ids for plans, suites, and configurations as well: •List plans tcm plans /list /collection: /teamproject:"Expense Reporting" •List suites Tcm suites /list /collection: /teamproject:"Expense Reporting" •List configurations tcm configs /list /collection: /teamproject:"Expense Reporting" © GSAtrain

Demo Creating a Test Project
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Demo Creating a Test Project Premium-and-Ultimate-Overview/Visual-Studio-Ultimate Easily-testing-user-interfaces-with-Coded-UI-tests © GSAtrain

Components of a Test Plan
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Components of a Test Plan © GSAtrain

Benefits of Automated Testing
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Benefits of Automated Testing Automated tests can quickly test whether your application is still working correctly after code changes have been made to your application Automating Test should not take more than about 40% of team members' time © GSAtrain

The Achilles’ heel of automated tests
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals The Achilles’ heel of automated tests The problem with user interface tests is not in how to execute them, but what to test. Since human testers would often check the whole round-trip of information, from the GUI to the back-end report First instinct is to replicate that and try to verify business domain rules. This is the Achilles’ heel of UI tests, and it ultimately leads to enormous waste of time. © GSAtrain

UI Testing without shooting yourself in the foot
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals UI Testing without shooting yourself in the foot © GSAtrain

Thinking About These Different Levels
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Thinking About These Different Levels The idea of thinking about these different levels is good because it allows us to write UI-level tests that are easy to understand, efficient to write relatively inexpensive to maintain Checking that delivery is available for two books involves putting a book in a shopping cart. Putting a book in a shopping cart involves a sequence of technical steps. Entering address details does as well. Breaking things down like that and combining lower level concepts into higher level concepts reduces the cognitive load and promotes reuse. © GSAtrain

Using Microsoft Test Manager
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Using Microsoft Test Manager You can plan, manage and execute both manual and exploratory tests. You can also automate your manual tests after they are stabilized. While you are performing manual and exploratory tests, you can log bugs. The bug will contain a trace of your recent actions, a snapshot of the state of the system, and a copy of any notes you made while exploring the system. You can record your actions in the test case, so that they can be played back on later occasions. © GSAtrain

Module 1 – Introducing the Fundamentals With Visual Studio 2012 Lab Management it is possible to create an environment based on existing infrastructure without installing SCVMM. This is great because we can now start using Lab Management without any additional installation required. The lab machines in a standard environment can be physical or virtual (or both) and the virtual machine does not have to be managed by SCVMM or Hyper-V. To create a standard environment you only need to know the names of the machine you want to add to the environment and a user account to be used to log in and deploy the test agent service onto the machine. A standard environment can be connected to directly from MTM and the Test Runner making the integration with lab environments really smooth. © GSAtrain

Module 1 – Introducing the Fundamentals The alternative to standard environments is to use a SCVMM environment. The key features of a SCVMM environment include •Create new machines from templates. New lab machines can automatically be created by anyone (having permissions) running MTM. It is no longer required to send a request to the operations department to get machines created for a new environment or to do other maintenance operations such as starting, stopping, snapshotting, or restoring machines. •Support for snapshots. It is possible to work with snapshots from MTM, which enable testers to save state during testing. This is a powerful feature both to unlock the tester if a test case fails (no need to block an environment while waiting for a resolution) but also to give a developer a fixed point in time to reproduce a bug. •Connection inside MTM. A SCVMM environment can be connected to MTM and the Test Runner just like with the standard environment. © GSAtrain

Module 1 – Introducing the Fundamentals There are a number of metrics to can use as KPIs for software testing. •Number of bugs per state. How many bugs do we have that are active, resolved, or closed? Are the number of active bugs increasing and number of resolved and closed bugs constant? Then we need to look into how we perform our testing. •Number of bugs sent back from testers for more information. A large number might indicate that communication between developers and testers must improve. •Code coverage. This shows us how much of the code has been covered by our automated unit tests. We get the value as a percentage of the whole code. •Tests run results. How are our tests performing? Do we have many failed tests? If so, what can we do to improve this? •Percent Requirements covered by test cases. Do we write test cases for all our requirements? If not, what is the reason? •Percent Requirements covered by testing. Do we actually run the tests we have test cases for? If this figure is low and the figure for Percent Requirements covered by test cases is high we might have an issue we need to deal with. © GSAtrain

Module 1 – Introducing the Fundamentals The application tier is the core of TFS. Here we find all services TFS offers. First we find all web services for team project collections. We all recognize this so no further explanation is necessary: •Version control •Build service •Lab management •Work Item tracking •Team Foundation Framework services. This set of services is running on the Application Tier of TFS and allows us to access the different aspects of Team Foundation Server, including administration, security, and events. They enable us to extend Team Foundation functionality by developing TFS extensions and adapters to integrate third-party tools with TFS 2012. We also find the Application Web services: © GSAtrain

Module 1 – Introducing the Fundamentals The Tester’s Benefits After you have run your tests, you can report on your progress. When you use test plans to structure your testing approach, you can answer the following questions: How many tests have passed or failed? How many tests still have to be run for this iteration? When will the testing be complete? Which areas of the product have high test failure rates? Which test configurations have high test failure rates? Who has the most tests left to be run? Can resources be reallocated to better balance the remaining testing? Which build should the testers be using based on code changes and bug fixes? © GSAtrain

Essential Guide for Running Automated Tests from a Test Plan
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Essential Guide for Running Automated Tests from a Test Plan © GSAtrain

Module 1 – Introducing the Fundamentals Creating a CUIT Coded UI Test You perform the test manually while CUIT Test Builder runs in the Background You can Specify the Values that should appear in specific fields The CUIT Test Builder Records actions and generates Code Your Main Skills are in Testing not Coding © GSAtrain

Module 1 – Introducing the Fundamentals If you are a Developer You can extend the CUIT code The CUIT Test Builder builds Structured Code Straightforward to copy and adapt © GSAtrain

Defining Your Testing Effort Using Test Plans
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Defining Your Testing Effort Using Test Plans Microsoft Test Manager enables you to do three important tasks, as shown in the following illustration: © GSAtrain

Module 1 – Introducing the Fundamentals Exploratory testing Exploratory testing seeks to find out how the software actually works, and to ask questions about how it will handle difficult and easy cases. The quality of the testing is dependent on the tester's skill of inventing test cases and finding defects. The more the tester knows about the product and different test methods, the better the testing will be. © GSAtrain

Benefits of Exploratory Testing
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Benefits of Exploratory Testing The main advantage of exploratory testing is that less preparation is needed, important bugs are found quickly, and at execution time, the approach tends to be more intellectually stimulating than execution of scripted tests. Another major benefit is that testers can use deductive reasoning based on the results of previous results to guide their future testing on the fly Another benefit is that, after initial testing, most bugs are discovered by some sort of exploratory testing. This can be demonstrated logically by stating, "Programs that pass certain tests tend to continue to pass the same tests and are more likely to fail other tests or scenarios that are yet to be explored.“ WikiPedia © GSAtrain

DrawBacks of Exploratory Testing
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals DrawBacks of Exploratory Testing Disadvantages are that tests invented and performed on the fly can't be reviewed in advance (and by that prevent errors in code and test cases), and that it can be difficult to show exactly which tests have been run. Freestyle exploratory test ideas, when revisited, are unlikely to be performed in exactly the same manner, which can be an advantage if it is important to find new errors; or a disadvantage if it is more important to repeat specific details of the earlier tests. This can be controlled with specific instruction to the tester, or by preparing automated tests where feasible, appropriate, and necessary, and ideally as close to the unit level as possible. © GSAtrain

Module 1 – Introducing the Fundamentals Exploratory Testing Exploratory testing is particularly suitable if reuirements and specifications are incomplete, or if there is lack of time.[7][8] The approach can also be used to verify that previous testing has found the most important defects.[7] © GSAtrain

Visual Studio and Exploratory Testing
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Visual Studio and Exploratory Testing Performing Exploratory Testing Using Microsoft Test Manager In Microsoft Test Manager open Testing Center Test Do Exploratory Testing I don't see “Do Exploratory Testing” Your team is using a version of TFS prior to 2012. © GSAtrain

Lesson 2 Coded User Interface Testing
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Lesson 2 Coded User Interface Testing Automated Functional Tests – Using CUIT Create a CUIT from Scratch Create a CUIT from action recording Making CUIT more Robust and Flexible © GSAtrain

Contents of a Coded UI Test
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals Contents of a Coded UI Test When you create a Coded UI Test, the Coded UI Test Builder creates a map of the user interface under test, and also the test methods, parameters, and assertions for all tests. It also creates a class file for each test. © GSAtrain

5) Automating Test Cases
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals 5) Automating Test Cases Automating the Calculator © GSAtrain

Module 1 – Introducing the Fundamentals Planning and Tracking Architecture, Modeling, and Design Developer Tools Testing Team Foundation Build Version Control What's New for Application Lifecycle Management in Visual Studio 2012 Visual Studio 2012 Other Versions Visual Studio 2010 Visual Studio 2008 2 out of 2 rated this helpful - Rate this topic You can use Visual Studio Application Lifecycle Management (ALM) to manage your product lifecycle, reduce risks, and improve efficiencies. When you install or upgrade to Visual Studio Team Foundation Server 2012, you and your team can benefit from the new features and supported tasks outlined in the following table. Lifecycle area New features and supported tasks Planning and Tracking Create and manage the product backlog, sprints, and tasks. Run daily standups with a task board. Support multiple teams within a team project. Engage stakeholders to provide feedback about pre-release software. Illustrate requirements with PowerPoint Storyboarding and link storyboards to work items. Manage enterprise project portfolios and access up-to-date project status and resource availability using Microsoft Project Professional and Project Server. Architecture, Modeling, and Design Create, read, and edit dependency graphs faster and more easily. Get more information about your work by opening and viewing linked model elements in work items. Communicate with others about the design by creating UML class diagrams from C# code. Implement your design more quickly by generating C# code from UML class diagrams. Import UML class, use case, and sequence diagram elements from XMI 2.1 files. Developer Tools Work more efficiently by organizing work and reducing the impact of interruptions using My Work and Pending Changes. Enhance transparency and collaborate more effectively to product quality code using Code Review. Integrate testing into the developer workflow using Test Explorer. Find duplicated code in a solution with Code Clone Analysis. Collect diagnostic data for applications running on computers that don't have Visual Studio by using the IntelliTrace standalone data collector. Review Web requests in IntelliTrace recordings for ASP.NET Web applications hosted on IIS 7.0 or later. Easily debug code generated from text templates. Quickly customize the code generator by writing Visual Studio extensions. Testing Conduct exploratory test sessions. Locate, view, and edit your test methods, UI actions and their associated controls in the UI control map. Quickly track your test plan progress using the Results tab in Microsoft Test Manager. Clone your test plan to work on different releases in parallel. Test Windows Store apps running on a remote device using manual tests or exploratory test sessions. Install and configure agents more easily for Lab Management for Visual Studio 2012. Include SCVMM 2012 and clustered Hyper-V hosts in Lab Management for Visual Studio 2012. Team Foundation Build Define and run automated build processes in a hosted deployment of TFS by connecting it to an on-premises or hosted build controller. Increase the efficiency of your gated check-in build process by configuring it to build multiple check-ins at the same time. Run native and third-party framework unit tests using Visual Studio Test Runner or RunTests in a custom build process. Easily access, organize, and get information about the builds that matter most to you using the Builds page in Team Explorer. Debug builds more easily. Version Control Work in local workspaces either in or outside of Visual Studio, even when you're not connected to Team Foundation Server. Manage your work, reduce the impact of interruptions, and facilitate collaboration with your team with My Work and Pending Changes pages in Team Explorer. Conduct and track reviews of active, suspended, or checked-in code. Manage shelvesets and changesets using My Work and Pending Changes. Review and modify code changes more easily using the enhanced Diff window. © GSAtrain

Module 1 – Introducing the Fundamentals Testing New in VS 2012 Conduct exploratory test sessions. Locate, view, and edit your test methods, UI actions and their associated controls in the UI control map. Quickly track your test plan progress using the Results tab in Microsoft Test Manager. Clone your test plan to work on different releases in parallel. Test Windows Store apps running on a remote device using manual tests or exploratory test sessions. Install and configure agents more easily for Lab Management for Visual Studio 2012. Include SCVMM 2012 and clustered Hyper-V hosts in Lab Management for Visual Studio 2012. © GSAtrain

6 Automating Coded UI Tests
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals 6 Automating Coded UI Tests © GSAtrain

12) New Visual Studio 2012 ALM Features
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals 12) New Visual Studio 2012 ALM Features Planning and Tracking Architecture, Modeling, and Design Developer Tools Testing Team Foundation Build Version Control What's New for Application Lifecycle Management in Visual Studio 2012 Visual Studio 2012 Other Versions Visual Studio 2010 Visual Studio 2008 2 out of 2 rated this helpful - Rate this topic You can use Visual Studio Application Lifecycle Management (ALM) to manage your product lifecycle, reduce risks, and improve efficiencies. When you install or upgrade to Visual Studio Team Foundation Server 2012, you and your team can benefit from the new features and supported tasks outlined in the following table. Lifecycle area New features and supported tasks Planning and Tracking Create and manage the product backlog, sprints, and tasks. Run daily standups with a task board. Support multiple teams within a team project. Engage stakeholders to provide feedback about pre-release software. Illustrate requirements with PowerPoint Storyboarding and link storyboards to work items. Manage enterprise project portfolios and access up-to-date project status and resource availability using Microsoft Project Professional and Project Server. Architecture, Modeling, and Design Create, read, and edit dependency graphs faster and more easily. Get more information about your work by opening and viewing linked model elements in work items. Communicate with others about the design by creating UML class diagrams from C# code. Implement your design more quickly by generating C# code from UML class diagrams. Import UML class, use case, and sequence diagram elements from XMI 2.1 files. Developer Tools Work more efficiently by organizing work and reducing the impact of interruptions using My Work and Pending Changes. Enhance transparency and collaborate more effectively to product quality code using Code Review. Integrate testing into the developer workflow using Test Explorer. Find duplicated code in a solution with Code Clone Analysis. Collect diagnostic data for applications running on computers that don't have Visual Studio by using the IntelliTrace standalone data collector. Review Web requests in IntelliTrace recordings for ASP.NET Web applications hosted on IIS 7.0 or later. Easily debug code generated from text templates. Quickly customize the code generator by writing Visual Studio extensions. Testing Conduct exploratory test sessions. Locate, view, and edit your test methods, UI actions and their associated controls in the UI control map. Quickly track your test plan progress using the Results tab in Microsoft Test Manager. Clone your test plan to work on different releases in parallel. Test Windows Store apps running on a remote device using manual tests or exploratory test sessions. Install and configure agents more easily for Lab Management for Visual Studio 2012. Include SCVMM 2012 and clustered Hyper-V hosts in Lab Management for Visual Studio 2012. Team Foundation Build Define and run automated build processes in a hosted deployment of TFS by connecting it to an on-premises or hosted build controller. Increase the efficiency of your gated check-in build process by configuring it to build multiple check-ins at the same time. Run native and third-party framework unit tests using Visual Studio Test Runner or RunTests in a custom build process. Easily access, organize, and get information about the builds that matter most to you using the Builds page in Team Explorer. Debug builds more easily. Version Control Work in local workspaces either in or outside of Visual Studio, even when you're not connected to Team Foundation Server. Manage your work, reduce the impact of interruptions, and facilitate collaboration with your team with My Work and Pending Changes pages in Team Explorer. Conduct and track reviews of active, suspended, or checked-in code. Manage shelvesets and changesets using My Work and Pending Changes. Review and modify code changes more easily using the enhanced Diff window. © GSAtrain

10) Upgrading Coded UI Tests from Visual Studio 2010
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals 10) Upgrading Coded UI Tests from Visual Studio 2010 © GSAtrain

11) Extending Coded UI Tests and Action Recordings
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals 11) Extending Coded UI Tests and Action Recordings © GSAtrain

12) Testing Large Applications with Multiple UI Maps
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals 12) Testing Large Applications with Multiple UI Maps © GSAtrain

13) Using HTML5 Controls in Coded UI Tests
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals 13) Using HTML5 Controls in Coded UI Tests © GSAtrain

14) Using WPF with Coded UI Tests
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals 14) Using WPF with Coded UI Tests © GSAtrain

15) Best Practices for Coded UI Tests
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals 15) Best Practices for Coded UI Tests © GSAtrain

16) Using the Coded UI Test Logs
IOS Development for iPhone and iPad iOS 6 Module 1 – Introducing the Fundamentals 16) Using the Coded UI Test Logs What's New for Application Lifecycle Management in Visual Studio 2012 Visual Studio 2012 Other Versions Visual Studio 2010 Visual Studio 2008 2 out of 2 rated this helpful - Rate this topic You can use Visual Studio Application Lifecycle Management (ALM) to manage your product lifecycle, reduce risks, and improve efficiencies. When you install or upgrade to Visual Studio Team Foundation Server 2012, you and your team can benefit from the new features and supported tasks outlined in the following table. Lifecycle area New features and supported tasks Planning and Tracking Create and manage the product backlog, sprints, and tasks. Run daily standups with a task board. Support multiple teams within a team project. Engage stakeholders to provide feedback about pre-release software. Illustrate requirements with PowerPoint Storyboarding and link storyboards to work items. Manage enterprise project portfolios and access up-to-date project status and resource availability using Microsoft Project Professional and Project Server. Architecture, Modeling, and Design Create, read, and edit dependency graphs faster and more easily. Get more information about your work by opening and viewing linked model elements in work items. Communicate with others about the design by creating UML class diagrams from C# code. Implement your design more quickly by generating C# code from UML class diagrams. Import UML class, use case, and sequence diagram elements from XMI 2.1 files. Developer Tools Work more efficiently by organizing work and reducing the impact of interruptions using My Work and Pending Changes. Enhance transparency and collaborate more effectively to product quality code using Code Review. Integrate testing into the developer workflow using Test Explorer. Find duplicated code in a solution with Code Clone Analysis. Collect diagnostic data for applications running on computers that don't have Visual Studio by using the IntelliTrace standalone data collector. Review Web requests in IntelliTrace recordings for ASP.NET Web applications hosted on IIS 7.0 or later. Easily debug code generated from text templates. Quickly customize the code generator by writing Visual Studio extensions. Testing Conduct exploratory test sessions. Locate, view, and edit your test methods, UI actions and their associated controls in the UI control map. Quickly track your test plan progress using the Results tab in Microsoft Test Manager. Clone your test plan to work on different releases in parallel. Test Windows Store apps running on a remote device using manual tests or exploratory test sessions. Install and configure agents more easily for Lab Management for Visual Studio 2012. Include SCVMM 2012 and clustered Hyper-V hosts in Lab Management for Visual Studio 2012. Team Foundation Build Define and run automated build processes in a hosted deployment of TFS by connecting it to an on-premises or hosted build controller. Increase the efficiency of your gated check-in build process by configuring it to build multiple check-ins at the same time. Run native and third-party framework unit tests using Visual Studio Test Runner or RunTests in a custom build process. Easily access, organize, and get information about the builds that matter most to you using the Builds page in Team Explorer. Debug builds more easily. Version Control Work in local workspaces either in or outside of Visual Studio, even when you're not connected to Team Foundation Server. Manage your work, reduce the impact of interruptions, and facilitate collaboration with your team with My Work and Pending Changes pages in Team Explorer. Conduct and track reviews of active, suspended, or checked-in code. Manage shelvesets and changesets using My Work and Pending Changes. Review and modify code changes more easily using the enhanced Diff window. © GSAtrain

Automating UI Testing Using Visual Studio 2012 Clive G Hermann

Similar presentations

Presentation on theme: "Automating UI Testing Using Visual Studio 2012 Clive G Hermann"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Automating UI Testing Using Visual Studio 2012 Clive G Hermann

Similar presentations

Presentation on theme: "Automating UI Testing Using Visual Studio 2012 Clive G Hermann"— Presentation transcript:

Similar presentations

About project

Feedback