Problem:

I used the "Do Exploratory Testing" freature of Microsoft Test Manager (MTM) but only the last 10 steps show up when I create a test case.

Solution:

In the new test case window press the "Change steps" button above the test steps.  This will bring up a dialog box allowing you to select additional steps.

Explanation:

The default number of steps to include in a test case is 10. That value is in the mtm.exe.config file:

<!-- The number of actions selected by default when a bug or test case is created
         while exploring the app or providing feedback. The number of actions displayed by default are
         four times this number -->
    <add key="DefaultNumberOfActions" value="10"/>

Problem:

I have a test controller in a domain and a test agent in a workgroup and I can’t register the agent with the controller.

Solution:

Create shadow accounts on the agent machine and on the controller machine that are in the Administrators Group.  Shadow accounts are accounts with the exact same name and password.

You can test your shadow account by trying to map to a share on the controller machine from the agent machine.  Try to access \\controlerMachine\c$  when you are challenged for credentials use the shadow account.  Note you may have to disable your firewall to perform this test.

Install and configure the controller on the controller machine.  In the Configure Controller dialog use your TFS account and select the project collection. Using Microsoft Test Manager (MTM) under the Lab Center tab verify that your controller is registered on the controller tab.

Second log in to the test agent machine as the shadow account and install and configure the test agent with the test controller.  When asked for a user name use the shadow account again. Using MTM refresh the contoller and you should see the Test Agent listed.  This machine is now ready to be used in Lab to create a physical environment.

Problem:

I have preconditions for a test case in Microsoft Test Manager (MTM) but I don’t know where to store or how to notify the tester before executing the test.

Solution:

Attach a preconditions document to the first step of your test case or create the preconditions as a shared step.

Explanation:

When creating a Test Case in MTM you can have attachments on each test step in a test case.  One solution to the problem of preconditions is to attach a document that contains the preconditions to the first step of your test case.  Now when the tester begins the test case the first step will be presented with a link to the preconditions document.  From there the tester can simply click the link to open the document and perform the necessary preconditions for the test case.

This same method can be used for any post conditions as well be attaching a document to the final step of the test case.

Another option is to create the preconditions as shared steps and include them as the first step in the test case.