Did you know that you have the option of either saving all Video Recording or just saving when you create a bug?
Check the Video Recorder configuration button and set up when you want to save recording plus the quality of the video.
The default is set to save all video recording.
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.
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.
Microsoft Test Manager 2010 is now available, thank you Microsoft. MTM like Visual Studio connects to Team Foundation Server where all artefacts are stored. Like the bug, test cases are work items. What else does MTM have, lots. Lets look at the concept of a test plan first. You can have one test plan to many for a project. It is totally up to you the test team how you set up your testing effort on a project.
The Test Plan documents the test effort thru:
- Properties: test environment, settings, configurations, assigned build, and details like state.
Test Suites: organize test cases. There are three types of test suites; one is based on a requirement, another is a query of work item fields and the third is static. The possibilities are endless.
Microsoft has taken the test plan document to the next level. You can update a test plan as test efforts change. You can copy it as a starting point for the next project. You can if needed extract the information into a word document using an add on tool. If your printing for management or auditor put it on the network and direct people to it – save the tree’s. Plus, I bet most people do not even read them.
Look out world the Test Plan has evolved. :-)