Manual testing with Test Manager 2010

Here is a summary of what I was shown today regarding the test manager 2010.

• Test Suites are configured with a set of test cases



• Test cases can be configured to capture all sorts of data, including Intellitrace, System Info (e.g. CPU, RAM, etc), Video Recording of steps, Test Impact (this is what DLL are being tested and if there is a change to one of them, the test manager lets you know that you might want to retest).



• You can set up different roles for each test suite/case. So you can have different permissions or setups.



• You can set up the suites to says what different configurations are needed, such as Firefox, IE7, IE8, etc..



• When you create a new test case, you can insert steps, such as click here open this, type that.



• AND you can create parameters for some of your steps, for example if you want to test an address form with different countries addresses, you just set up the parameters @address1,@address2,@city, etc... then create what values you want to test for those parmeters and save them as part of the test case.



• You can also set up "expected results" and you can put screen shots there.



• You then "Run" the test case where you select lightweight or full (determines how much data is collected).



• When running it will prompt you to create an "action recording" which records every click and action the tester does.



• When the tester tool is running and it comes to the step with the parameters, you can simply copy and paste from the values list.



• Once succcessfully run once, you can rerun automatically with different pararmeters.


• All the data collected can be attached to TFS bugs so that the developers will be able to see exactly what the tester did.



• Test Impact Analysis tells the tester that a new build may have affected a previously tested piece of code.

Tomorrow we talk about test automation.