
- •Tester guide
- •Version.1.0
- •Notions
- •Installation of applications
- •Migrate Test-Cases and Requirements to mtm (tfs)
- •Getting Started in Microsoft Test Manager 2013
- •Creating a Test Plan
- •Creating a Test-Case
- •Inserting shared steps to a Test-Case.
- •Performing manual testing
- •Configure Test Plan for manual testing
- •Running manual test
- •Running automated tests
- •Configure Test Plan for automated testing
- •Automate a test case
- •Recording your actions during a test run
- •If you make a mistake
- •If the test includes shared steps
- •If the steps include parameters
- •7.2.2. Link Coded ui test with Test-Case
- •7.2.2.1 Generate Coded ui test from a Test-Case
- •7.2.2.2 Add Coded ui test to Source Control
- •7.2.2.3 Coded ui test and Test-Case
- •Create Build Definition Step 1. Create a new build Definition
- •Setting a lab environment in mtm Lab Center
- •8.1. Create a lab environment
- •Create a release Build
- •Create a release template
- •Queue a Release Build
- •Coded ui Test
- •Creating a new Coded ui Test Project
- •Data Driven Coded ui test
Tester guide
Tester manual guide for
Manual and automated testing
Version.1.0
Table of Content
1. Introduction 6
1.1 Objectives of the present Manual 6
2. Abbreviations, acronyms and notions used in Guide 6
2.1. Abbreviations and acronyms 6
2.2. Notions 6
3. Installation of applications 8
4. Starting with Case Complete 11
4.1. Creating a Use Case 11
4.2. Creating a Test Case 11
4.3. Adding Requirements to a Use-Case 12
4.4. Creating Requirements 12
4.5. Migrate Test-Cases and Requirements to MTM (TFS) 13
5. Getting Started in Microsoft Test Manager 2013 15
5.1. Creating a Test Plan 15
5.2. Creating a Test-Case 16
6. Performing manual testing 19
6.1. Configure Test Plan for manual testing 19
6.2. Running manual test 21
7. Running automated tests 23
7.1. Configure Test Plan for automated testing 23
7.2. Automate a test case 24
7.2.1. Recording your actions during a test run 25
7.2.2. Link Coded UI test with Test-Case 27
7.2.2.1 Generate Coded UI test from a Test-Case 27
7.2.2.2 Add Coded UI test to Source Control 29
7.2.2.3 Coded UI test and Test-Case 32
7.3. Create Build Definition 34
Step 1. Create a new build Definition 34
8. Setting a lab environment in MTM Lab Center 37
8.1. Create a lab environment 37
9. Creating Release Work Flow in Release Management 2013 41
9.1. Set up Stages 41
9.2. Set up servers and environments 41
9.2.1. Register servers 41
9.2.2. Create environments 42
9.2.3. Create a release path 43
9.2.4. Create a release Build 44
9.2.5. Create a release template 45
9.3. Queue a Release Build 50
10. Coded UI Test 51
10.1. Creating a new Coded UI Test Project 51
10.2. Data Driven Coded UI test 52
This is a Quick Start Guide for manual testing. The guide helps you get started quickly by describing how to create manual tests, run them and record the results by using Microsoft Test Manager. 59
http://msdn.microsoft.com/en-us/library/vstudio/dd380763(v=vs.110).aspx 59
To install Visual Studio, you can use the installation media—for example, DVDs—or you can download the installation files from the Microsoft website. 59
http://msdn.microsoft.com/en-us/library/e2h7fzkw.aspx 59
In this walkthrough you will learn the procedures that are used to configure a test setting that uses a test controller and test agents to distribute a load test across several machines. Additionally, this walkthrough demonstrates how to add diagnostic and data adapters to the test setting. 59
http://msdn.microsoft.com/en-us/library/ff400223.aspx 59
Managing Test Controllers and Test Agents with Visual Studio 59
http://msdn.microsoft.com/en-us/library/dd695837.aspx 59
Using 59
Microsoft Test Manager 2013. 59
Manual Testing To Full Automation 59
This video clip describes how to plan and perform tests and record the manual test, and Creating Code UI, and test automation 59
https://www.youtube.com/watch?v=C3BnnR42lHA 59
Automate a test case in Microsoft Test Manager 59
http://msdn.microsoft.com/en-us/library/dd380741.aspx 59
Creating a Data-Driven Coded UI Test. 59
And add on .CSV file. 59
To test different conditions, you can run your tests multiple times with different parameter values. Data-driven coded UI tests are a convenient way to do this. You define parameter values in a data source, and each row in the data source is an iteration of the coded UI test. The overall result of the test will be based on the outcome for all the iterations. For example, if one test iteration fails, the overall test result is failure. 59
http://msdn.microsoft.com/en-us/library/ee624082.aspx 59
and video: 59
https://www.youtube.com/watch?v=FW2VADmeOoI 59
In the video clip explains how to add a .CSV file 59
https://www.youtube.com/watch?v=fvpxuVrrlEU 59
Load Testing 59
Use load testing in Visual Studio Ultimate to find performance issues before you release your app. 59
http://msdn.microsoft.com/library/dn250793.aspx 60
and video: 60
https://www.youtube.com/watch?v=37x8cHK7qLU 60
Standard lab environments 60
A standard lab environment is a collection of computers that can be managed as a group, as part of your tests. The computers can be physical or virtual Windows machines. 60
http://msdn.microsoft.com/en-us/library/ee390842.aspx 60
Automating Builds with TFS Build Definitions 60
Here comes the description of the case for the creation of build 60
http://boldradius.com/blog-post/UwOLcQEAAJV04Pl3/automating-builds-with-tfs-build 60
and video: 60
https://www.youtube.com/watch?v=zfSKeMU29CA 60
Release Management for Visual Studio 2013 60
Support a rapid release cadence and manage simultaneous releases. Set up release paths that represent your stages from development to production. Run actions to deploy your app to an environment for that stage. Add approvers to sign off that the app has successfully passed each stage. 60
http://msdn.microsoft.com/en-us/library/dn594436.aspx 60
and video: 60
https://www.youtube.com/watch?v=6Y4DnNv6Kt0 60
1. Introduction 4
1.1 Objectives of the present Manual 4
2. Abbreviations, acronyms and notions used in Guide 4
2.1. Abbreviations and acronyms 4
2.2. Notions 4
3. Installation of applications 6
4. Starting with Case Complete 9
4.1. Creating a Use Case 9
4.2. Creating a Test Case 9
4.3. Adding Requirements to a Use-Case 10
4.4. Creating Requirements 10
4.5. Migrate Test-Cases and Requirements to MTM (TFS) 11
5. Getting Started in Microsoft Test Manager 2013 13
5.1. Creating a Test Plan 13
5.2. Creating a Test-Case 14
6. Performing manual testing 17
6.1. Configure Test Plan for manual testing 17
6.2. Running manual test 19
7. Running automated tests 21
7.1. Configure Test Plan for automated testing 21
7.2. Automate a test case 22
7.2.1. Recording your actions during a test run 23
7.2.2. Link Coded UI test with Test-Case 25
7.2.2.1 Generate Coded UI test from a Test-Case 25
7.2.2.2 Add Coded UI test to Source Control 27
7.2.2.3 Coded UI test and Test-Case 30
7.3. Create Build Definition 32
8. Setting a lab environment in MTM Lab Center 32
8.1. Create a lab environment 32
9. Creating Release Work Flow in Release Management 2013 36
9.1. Set up Stages 36
9.2. Set up servers and environments 36
9.2.1. Register servers 36
9.2.2. Create environments 37
9.2.3. Create a release path 38
9.2.4. Create a release Build 39
9.2.5. Create a release template 40
9.3. Queue a Release Build 45
10. Coded UI Test 46
10.1. Creating a new Coded UI Test Project 46
10.2. Data Driven Coded UI test 47
Introduction
1.1 Objectives of the present Manual
The objective of this document is to guide testers into the entire process of testing, from creating Test-Cases, to performing manual and automated tests. As well in this document are described tools and applications necessary for creating and executing manual and automated tests.
Abbreviations, acronyms and notions used in Guide
Abbreviations and acronyms
Abbreviations and acronyms used in this document are defined and explained in the table below:
Abbreviation/Acronym |
Description |
TFS |
Team Foundation Server |
RM |
Release Management |
MTM |
Microsoft Test Manager |
VS |
Visual Studio |
CC |
Case Complete |
IIS |
Internet Information Services |