Skip to main content

Microsoft Test Manager – FUEL for test automation

(this is a follow-up post to this one: http://sudiptopaul.blogspot.com/2011/12/using-aspnet-page-state-and-theme-to.html)

Traditionally Test Management and Test Automation tools have been remotely related to each other.

Microsoft’s Test Manager changes this -
  1. Manual Testers contribute effectively by creating action recordings for each test
  2. Common portions of test steps can now be grouped into what is called as Shared Steps – again manual tester can create independent action recordings for these
  3. Test Manager enables these action recordings to serve as active inputs to test automation – separate class is created for each test case, and a reusable function for each shared step
    • This is very elegant as it saves the test automation engineer an amount of time required to refactor common portions of longish test path recordings
    • The Manual Tester gets to contribute in the Keyword definition phase – an important thing to do, because they are the subject matter experts!
Here’s a video that demonstrates this:
Microsoft Test Manager – FUEL for test automation
Labels:

Comments

Post a Comment

Popular posts from this blog

Experimenting with Visio and VBScript

This diagram is created:               using this code:                                                                         Copy the code: Option Explicit Dim strVSDPath, filesys Dim vsoApplication, vsoDocument, vsoPages, vsoPage Dim vsoMaster1, vsoMaster2, vsoStencil Dim vsoShape1, vsoShape2, vsoConnector1 Dim itr Const visAutoConnectDirDown = 2     'Connect down. Const visAutoConnectDirLeft = 3     'Connect to the left. Const visAutoConnectDirNone = 0     'Connect without relocating the shapes. Const visAutoConnectDirRight = 4     'Connect to the right. Const visAutoConnectDirUp = 1         'Connect up....
Post a Comment
Read more

QTP – search sub-folders for existence of QTP scripts

  Suppose we want to report on all subfolders in a specific root folder that contain script files. Consider the example folder structure here – ODBC_MYSQL, ODBC_SQLEXPRESS and Test1 are the folders that have QTP scripts: Here’s a VBScript program that takes the root (start) folder as input, and iterates all subfolders recursively to report on the ones that are actual QTP script folders: Note: This program can be run directly as a VBScript program, or from within a QTP script by toggling the comment between lines 17 and 18. (p.s.: if Print statement does not work on specific version of QTP, use the Msgbox statement. For real world test automation projects, do not use either – to avoid human intervention!) On running the program, Folders across various levels (Level 2, 3) get reported!
2 comments
Read more

Fresh brew with NUnit for Selenium over a cuppa VS2010 Express’o

  Selenese coffee beans 1) A recorded Selenium script for a simple scenario of googling for the term Tomato. This recording should have been saved as an export in C# format. 2) VS2010 express editors – for C# and Web dev 3) MS Excel 4) Browsers – Chrome, Firefox, IE 5) WebDriver for Google Chrome Prepare the Coffee Machine Let’s install NUnit extension, NuGet package manager, Selenium packages and include MS Excel Interop reference into VS2010. Essentially 2 different editors are required from the VS2010 stable: a) Microsoft Visual C# 2010 Express – get NUnit b) Microsoft Visual Web Developer 2010 Express – to get NuGet and Selenium   Let’s get started with Microsoft Visual C# 2010 Express – Invoke Extension Manager: Browse the Online Gallery and download NUnit Test Application: Install NUnit: Confirm that installation succeeded: and this page is displayed in your default browser: Choose to create a New Project: Select th...
Post a Comment
Read more