CATEGORIES:
BiologyChemistryConstructionCultureEcologyEconomyElectronicsFinanceGeographyHistoryInformaticsLawMathematicsMechanicsMedicineOtherPedagogyPhilosophyPhysicsPolicyPsychologySociologySportTourism
Installation of applications
Tester manual guide for
Manual and automated testing
Version.1.0
Table of Contents
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
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 |
Notions
Definitions of notions frequently used in Guide are described and explained in the table below:
| Abbreviation / Acronym | Description |
| Team Foundation Server | Is a Microsoft product which provides source code management (either via Team Foundation Version Control or Git), reporting, requirements management, project management (for both agile software development and waterfall teams), automated builds, lab management, testing and release management capabilities. It covers the entire Application Lifecycle Management. |
| Microsoft Test Manager | This is a visual studio application (Visual Studio Test Professional 2013) where you can plan, manage, and execute manual, automated and exploratory tests. While 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 later. |
| Release Management | This is a Microsoft application in visual studio which helps with process of managing software releases from development stage to software. With RM you can automatically configure, approve and deploy your applications for any environment. Create automated deployment orchestrations for each environment no matter how complex the configuration. |
| Case Complete | Is a requirements management application from Serlio Software that allows business analysts and software developers to create and manage Use Cases and Software Requirements. CaseComplete provides the ability to edit the textual portion of use cases and requirements in a guided environment and the ability to create various types of diagrams including use case diagrams, wireframes of graphical user interfaces, and flowcharts. |
| Lab Environment | A 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. Lab environments are used when testing an application that runs on servers, such as a web application. Lab environments collect diagnostic data from the server machines while test perform on local client machine. |
| Build | Process of converting source code files into standalone software artifact(s) that can be run on a computer, or the result of doing so. |
| Build Definition | A build template wherein is described parameters and options for creating new Builds. |
| Build Process Template | Is a Windows Workflow 4.0 xaml file template that contains described processes on how to build code, run tests, and run other processes such as scripts. |
| Test Controller | The test controller distributes tests and manages test runs by communicating with the test agents on each test machine. In addition, test controllers enable you to use diagnostic data adapters to collect data or impact the test machine when the tests are run. |
| Test Agent | Test agent is used to perform tasks such as installing software, running tests, and collecting test data. |
| Coded UI test | Coded UI tests are automated User Interface tests that can be created with Visual Studio to test different kinds of user interface. |
| Test-Suite | Is a collection of test cases that are intended to be used to test a software program to show that it has some specified set of behaviours. A test suite often contains detailed instructions or goals for each collection of test cases and information on the system configuration to be used during testing. |
| Test-Case | A test case is a document, which has a set of test data, preconditions, expected results and postconditions, developed for a particular test scenario in order to verify compliance against a specific requirement. A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly. |
| Use Case | Is a list of steps, typically defining interactions between a role (known in Unified Modeling Language (UML) as an "actor") and a system, to achieve a goal. The actor can be a human, an external system, or time. |
Installation of applications
1. Microsoft Test Manager 2013:
1.1 Download MTM 2013 from http://www.microsoft.com/en-us/download/details.aspx?id=40784.
Note:Visual Studio Ultimate 2013 itself contains Microsoft Test Manager 2013, so no installation is required.
1.2 Open Microsoft Test Manager and add Team Foundation Server.
2. Test Controller and Test Agent:
2.1 Download install from http://www.microsoft.com/en-us/download/details.aspx?id=40750 .
2.2 Install test-controller on the the server on which it will be run.
2.3 Open the Test Controller Configuration Tool and complete the fields:
2.4 Save and wait until the configuration takes place.
Note:The account which will be used by test agents to communicate with the controller must be a member of the Administrators Group.
2.5 Install Test Agents on the machines of a lab environment.
2.6 Open the Test Agent Configuration Tool and complete the fields:
Tips:
- The user which is specified in Machines and Advanced step must be a member of the Administrators group on all the selected machines.
- Machines which are added to the environment must be registered in the domain.
3. Release Manager client 2013.
3.1 Download install RM 2013 client from http://go.microsoft.com/fwlink/?LinkId=512595 and install client on the local computer.
3.2 Start the Release Management Client and connect to tfs2013.alfa.local.
4. Microsoft Deployment Agent 2013.
4.1 Download deployment agent from http://go.microsoft.com/?linkid=9843010 and install to any machine that will be part of the environment used to deploy your app.
4.2 Open the Microsoft Deployment Agent 2013 and complete the fields:
Note:The Deployment Agent Service Account must be a member of the Administrators Group.
Date: 2015-12-24; view: 793
| <== previous page | | | next page ==> |
| | | Configure Test Plan for manual testing |