Microsoft Test Manager(MTM) – multiple instances on desktop

At this time you cannot have more then one instance of Test Manager open on a desk top with out doing the following:

Made another copy of the MTM.exe and MTM.exe.config  files found on your C:\ drive under Microsoft Visual Studio 10.0\Common7\IDE

Then you have two instances of Test Manager for opening, this comes in handy when you need to look at different area’s of MTM at the same time.

Testa Smile

Microsoft Test Manager and Infragistic Controls

If your developers are using Infragistic controls and your using Test Manager you will not be able to create action recording. Jeff Levinson advised me that:

“Playback won’t work with the infragistics controls (unless it is a web app because MTM actually works against the DOM in a web app and not against the controls directly). The Infragistics controls won’t be recognized if you try to add them to a UIMap (again – unless this is a web app) because they don’t support the interfaces to allow MTM to interrogate the control.”

You can however play around with the Coded UI tests. A client I recently worked with was able to create CUI test recordings and play them back where Infragistic controls existed. Note this was not using action recordings to create.

If your development team is using Infragistic controls please contact Infragistics requesting they add the interfaces to allow MTM to interrogate their controls. Telerik at this time is the only company that has added support for their controls and MTM.

Testa Smile

Microsoft Test Manager (MTM) – Test Case steps

I am seeing people talking about having a test case with up to 50 and even 100 steps. I might be mad but isn’t that a lot of steps in one test case? When I talk to test teams my recommendation is no more then 10 steps per test case.

Make usage of Shared Steps that can be used to navigate through an application. Make usage of other test cases that will get your test case to the right spot in the application. Use the MTM ordered test feature to organize test cases to run in a specific sequence when needed.

I like to tell testers about the KISS principle of design.

Keep it simple and straightforward.

Keep it simple and short.

The KISS principle states that simplicity should be a key goal in design, and that unnecessary complexity should be avoided. This applies to code design as well.

Test Cases you’ve kissed will be easy to understand, maintain and report on.

Testa  Secret telling smile


Microsoft Test Manage MTM– test run pausing and resuming

Questions about the ability to pause a test case during execution then restart it has come up in discussions a few times. Thought I would share that it can be done and how.

In the Test Runner you click the Pause button…


In the Test Runner next click the Return to the Testing Center icon…


Once back in the Testing Center in the window header will be a new icon that when clicked returns you to the Test Runner ….


Clicking the Return to Test Runner icon opens Test Runner with a Resume button that when clicked starts your test execution where you left off.



Closing Test Manager  will close the paused test run and set it to Failed.

During a Test Run pause, if you start another Test Case Run the message below is posted. image

Save and/or Don’t Save ends the paused test run setting it to Failed. (original test run stops)

Cancel stops the newly select test case run and returns you to the Test Center with the icon displays to resume the original test.

If there are things about Test Manager you would like to see changed add a backlog item or vote on the one’s already added. Microsoft is looking for our input on what changes people want and by voting on them how important it is to you.

A backlog item already exists for allow you to pause one test run and start another then return to the paused run. If this is important to you click below find this backlog item and vote.

Visual Studio UserVoice

Testa Smile


The Testing Planet– The Evil Tester Question Time

Just released the July edition of The Testing Planet.

The Testing Planet - Issue 5 - July 2011

Available for your Kindle

Testa … enjoy reading about testing by testers.

TesTrek 2011 in Toronto – Nov. 7th to 10th

Sign up for an Object Sharp workshop on Exploratory Testing at TesTrek 2011 in Toronto, Ontario on November 11th at 1:30pm. Myself and Dave Lloyd will be presenting plus giving you hands on experience doing exploratory testing. See how to overcome the challenges of tracking the steps you took, reporting bugs and retesting exploratory bugs.

Experience and Overcome the Challenges of Exploratory Testing

In 1983, the term Exploratory Testing was introduced. Prior to that, we called it ad-hoc testing. Exploratory testing is said to be a mindset, a way of thinking, freestyle testing that liberates the tester to explore. Testers, through experience, know their applications inside out; they are the users in reality. Freeing testers to explore and use the application has been proven to identify more bugs then traditional scripted testing. However, there are obstacles and challenges related to this freestyle testing. Join this workshop to explore those obstacles hands on and learn how we can overcome them. Explore an application with known bugs and see if you can find them.

  • Experience exploratory testing using the Microsoft Test Manager Tool.
  • Do your own exploratory testing on a Virtual Machine in the cloud.
  • Discover the difficulties of exploratory testing, how to track the steps, report the bug, and perform retesting.
  • Participate in idea generation for overcoming the issues of exploratory testing.

Sign up for the first TesTrek hands-on workshop.

Testa Smile

Agile, Manage & Test–Stickyminds launches TechWell for the test community.

Sticky has launched a new site called TechWell for the Agile, Manage and Test communities. You can interact with others through blogs, forums and groups. Access videos, podcasts, articles, and more all pertaining to testing.

With todays changes in the Software Industry happening quickly testers are facing challenges in the skills they need. The future is Agile with a Scrum methodology and framework. Testers need to be ready and it is going to  happen quickly, in fact it has started already.

I recommend checking out TechWell and getting the scoop from your peers in the community. Click on TechWell to check out.


Microsoft Test Manager & TFS–copy test cases from one Team Foundation Server to another

Shai has done it again. In my last blog I explained a tool that lets you copy test cases & shared steps from one Team Project to another. We had a need to copy test cases from one team project to another where the project resided on different Team Foundation servers.

Shai in no time revised the tool to enable copy of test cases between projects residing in different TF servers.

If you have a need for this tool email me.

Great tool – thanks again Shai

Testa Smile


Microsoft Test Manager & TFS – copy test cases from one team project to another team project.

In Test Manager you can copy existing Test Suites into Test Plans but only when they are both in the same Team Project. You can also create a copy of a test case adding it to a different team project but only one at a time in Visual Studio or MTM. So what happens if I have test cases that are in other Team Projects that I want to add to a new Team Project?

Shai Raiten who is a VS ALM MVP & Microsoft Regional Specialist has created a tool for this function.

The tool is a wizard that walks you through the:

1 Connection to the Team Foundation Server
2 Selection of the Source Team Project (where test case to be copied reside)
3 Selection of the Target Team Project (where you are coping test cases too)
4 Selection of migrating existing test case links, attachments, areas, iterations and even the duplication of existing Shared Steps.
5 Addition of a Configuration File that saves the migration results
6 Field mapping – the wizard checks that the target test case work item has all the same fields as the source
7 If you selected to copy area and/or iteration the wizard checks that the same data exists in the new project, if it does not you shown what is missing and expected to add into the target team project.
8 Then you get to select the query from the source team project that contains the test cases you want to copy or it may just be all test cases from the source team project. Either way the test cases from your query are displayed with a checkbox. You are required for each test case displayed to check the one’s you want copied.
9 All that is left is to click Start

If your source test case has:

Parameter’s they are copied
Shared Steps they are duplicated but not the action recordings
Parameter data it is all copied
Action recording they are not copied
History it is not copied, the new tests case will show the date and time the create was done and all the data that was copied.

If you include the coping of links from your source to your target and the link is another work item from your source team project it does not get copied into the target team project.

If you would like to use this tool email me.

Shai great tool and thanks for providing me a copy.

Testa Smile

Migration to Microsoft TFS 2010 from Quality Center with Scrat

Quality Center has been the popular kid on the block over the years. Since Microsoft Test Manager came out in April 2010 it has and is giving QC a run for it’s money. Many companies are wanting to convert over to Microsoft TFS 2010 from Quality Center but are not sure how and do not want to lose existing artefacts.

SELA a Microsoft Gold Partner have created Scrat that will let you migrate full HP Quality Center projects into TFS2010 in days. Requirements, Bugs, Test Cases, Attachments and Links between items plus their interrelationship links can all be migrated to TFS 2010. Scrat is completely configurable to migrate what you want and need.

I personally have met a number of test teams that are converting to TFS2010 here are some comments being made about TFS2010 and Test Manger:

    • the collaboration between teams is outstanding
    • there is one place that stores all the project artefacts and anyone on the team can see them, how organized and commutative is that.
    • love the alerts, people know about bugs as soon as I save them
    • bug information automatically added would take me hours to put together
    • snap shot capability during test execution, no more folders full of screen prints
    • the test steps are added to the bug for me what a time saver
    • Test Impact – (normally it is the facial expression, such emotion, then demo it for people!)
    • now that I don’t have to manually note my steps during Exploratory testing, I can do a lot more testing and concentrate 100% on what I am doing

Note: the above are not direct quotes they are however truly what I am hearing testers saying.

Check out Scrat and if you need help give us a call.

Testa Smile