Home > Blogs
TesTrek in Toronto is coming this October check out the website at this link for more information.
Dave Lloyd and I are doing a workshop on October 20th at 11:00am - 12:30am
Effectively Managing the Testing Process through Collaboration
Debra Forsyth and Dave Lloyd,
Object Sharp Consulting
Communications is the key to the success or failure of any team, whether it’s a sports team or a software development team creating the next app. Without communication, the team members have no idea how best to direct their efforts. With communication, the team can overcome almost any challenge. Unfortunately, ensuring that the level of collaboration required in generating success can be a difficult goal to achieve. Solid development managers have a bag of tricks that they utilize to foster communications among the different roles. In this session, you will learn some of the tricks that can be used in your own environment to create better communications across all of the team roles.
- How can the other team roles more effectively communicate with the testing team?
- What does the test team need to know to complete the testing effort?
Special 15% Promotion Discount to TesTrek:
To receive a special 15% speaker promotion discount, please contact Darrin Crittington and give the special promotion code of ‘Spkpromo2010’ along with our names either by emailing dcrittington@qaiworldwide.org or calling 1-866-724-6013.
Testa
In my last blog there where questions about how to assign or unassigned test cases to test configurations (browsers, operating systems).
How to manage test case/test configuration assignment:
- In the Plan Tab select a test suite then test case.
- In the Test Suite panel toolbar click on the Configurations button.
- The Select Test Configurations window opens where you can add and remove test configurations associated to a test case.
- Simply click button All configurations, all test configurations you have created are added to the test case.
- Next click in the test configuration cell to add or remove.
- Last, click the Apply Changes button.
Whether you add test configurations before or after setting up Test Suites and Test Cases you can manage test case assignment by using the Test Suite | Test Case, Configurations button.
Note: Test Suite/Test Cases are automatically assigned to all test configurations created prior to there own existence.However, if you create additional test configurations after creating Test Suites/Test Cases they are not automatically assigned. In this case you can assign using the above steps.
Thanks to Jeff Levinson (Team System, MVP) for helping out with this question.
Testa
Duplication of tests for configurations does have a flow that you need to be aware of …
- Test Configurations have to be set to active and selected in the Test Plan properties.
- Test Configurations set up prior to creating test cases are automatically duplicated for each configuration assigned to the test plan.
- Note: you have no ability to indicate which configurations affect which test cases. Therefore you will have to use the test case run status of “blocked”. If you leave “active” a tester would be able to run.

-
Adding a new test configurations to an existing Test Plan will not affect any existing Test Suites. ( I believe this is a bug and have reported it to Microsoft) However, if I add a new test suite and associate existing or new test cases to that suite all the Test Plan test configurations are used.
When I get an answer on whether this the correct behaviour or if there is a work around will post it.
Testa
If you need to test against different test configurations you are going to love Microsoft Test Manager.
Test Configurations are different setups that any application requires testing against. Example: Microsoft Test Manager would have been tested against different operating systems like XP, Vista, or Windows7. A web application may require testing against different browsers like IE7, IE8, Fire Fox, Chrome or Safari.
The ability to set up test configurations is only limited to your needs. One of the best features is the ability of Microsoft Test Manager to simulate a duplication of test cases for test configurations assigned to a test plan for test runs only.
It does require management to some extend however;
- it does save your team time in creating duplicate test cases or excel spreadsheets of what configurations will or have been tested.
- it is only really one instance of the test case so an changes affect all instances in the test run.
- the test plan documents what configurations will been tested and by which test cases.
There is significant savings to the test team for this feature to be one of the top.
Test Plan – test case shows once only.
Test tab >Run Tests – test case is shown for each test configuration set up in our test plan.
Over the next few blogs I will tell you more about Test Configurations and how they affect test cases and test runs.
Testa
Learn about Web Performance Tests authoring & debugging with Visual Studio 2010. Ed Glas is the Load Test product team manger at Microsoft and has posted some very good reading material on the subject of web tests.
Web Test Authoring and Debugging Techniques for Visual Studio 2010
Great reading Ed … Testa
When attempting to paste (using Ctrl-V) data from the clipboard into a parameter within an Iteration you must use the spacebar or manually click into the field that you are populating. If you don't have a cursor blinking even thought the box is highlighted (has focus) using Ctrl-V creates another Iteration instead of pasting the copy data.
This bug has been report to Microsoft and should be address in a future update.
___________________________________________________________________________________
Created a Shared Step that has 37 parameters. We added the Shared Step to a Test Case and loaded the data for one iteration. We then decided to remove two parameters. In the Shared Steps we deleted the two parameters and removed the steps. Saved and Closed. We then opened the Test Case expected the two parameters to be gone, they are not.
We have also had issues with changing the data in the parameters (Test Case)
1 remove the data then click the enter key
2. add the new data then tab out
3. save.
Work a Round's:
1. Deletion of parameter in shared step does not delete parameters in the test case.
There is definitely a bug with refresh here. I will file this issue. To workaround this, insert a dummy step and delete it. You will see that parameters go away. Let me know if this works for you.
2. Deletion of data
I agree, we do not have a good experience of editing data. You will have to hit the enter key to take the test case to dirty state. Only after that the data gets saved.
Testa
Shared steps can have parameters however, before adding iterations of data there are considerations you need to take into account.
If you consider logically how this works, adding a bunch of parameters and data to a Shared Step will have that step repeat running through the data you added. Then once all iterations of the shared step complete your next test case step would run. Make sense.
- What if I want the Shared Step parameters to run with other parameters in my Test Case?
- What if I want to add data to my Test Case Shared Step parameters months later?
The cleanest and most flexible way I believe and have found is to add data (iterations) to my Shared Step parameters from within the Test Case. Remember a Shared Step can be used in any Test Case and therefore needs to be flexible.
Example:
A Shared Step with Parameters > no data (iteration) added.
Shared Step with Parameters (userid & password) inside the Test Case
Above there are three parameters of which two belong to the Shared Step, the other the test case. You can add many parameter iterations to this test case without affecting any other test case that contains the same shared step. (If the UserID and Pswd’s were in the shared step that step would keep opening and login for each iteration before doing the test case step two.)
I have seen cases where testing always uses the same UserID and Pswd for login. In that case having these as parameters set within a Shared Step makes sense. If a new set of credentials is issued you can easily change them in one place, quick and simple.
Note: now this is confusing. I set my parameters in a Shared Step added the Shared Step to a Test Case. In the Test Case the shared step parameters display however they do not show any data.
[I will try a scenario where parameters are set in the Shared Step and in the Test Case to see what happens! - will let you know the outcome]
Comments on this subject are welcome. If you have found a different way to handle a combination of parameters in shared steps and test cases or situations you have come across – lets learn together.
Testa :-)
This is a very cool feature and a big test effort time saver.
In your test plan you have set up more then one configuration. Maybe you need to test in different browser types, or different operating systems, even different languages. You create one test case to test a feature/requirement and attach it to a test suite, setting suite state to In Progress. When you go to the tab Test and open Run Tests there is an instance of your one test case for every configuration assigned to the Test Plan.

For very large applications or web sites that require testing in many different configurations this feature not only saves time in the creation of many test cases but it creates a marker that the testing has been done.
Feature Highlight:
Many Test Configurations – One Test Case – Instance of Test Case for every Test Configuration.
Creating or editing a Test Case in Visual Studio:
If you create a Test Case in Visual Studio you cannot enter steps, first enter a Title and save, then click the Open for edit button. Test Manager opens with the test case open ready for you to enter steps.
You can add links, file attachments and/or add to the summary from within Visual Studio.
Opening for edit a test case in Visual Studio does not allow you to edit the steps. Again you have to click Open for edit which opens the test case in Test Manager.
Creating or editing Shared Steps in Visual Studio works the same way as the Test Case.
Website Not Invented Here had a great comic worth sharing.
