The summary tab is preferred over the grid, which forces tests into individual steps with expected results. Most testers like to write their test cases as fragments, using the test case work item’s free-form summary tab.
#Microsoft team foundation server 2010 update#
Quality Center had something similar but provided an alternate method of updating execution status (i.e., one could bulk update via a grid). I can’t imagine anyone actually testing like this. This is the thing that shows you each test case step and asks you for a pass/fail result. To update the execution status of Test Manager tests, one must go through the ridiculous test case executor.It took too many clicks to get anything done. The screens frequently hung, causing some testers to force quit and re-launch. One of the most annoying parts of our Test Manager trial may have been its usability and performance.However, we were hoping Test Manager would trickle down the results to TFS so the whole team could benefit. In fact, it was one of the biggest motivators for us to try Test Manager. Test case run execution history is actually cool.
The reasoning behind this is probably Test Manager’s test cases can have test case run execution history (e.g., TestA could be passed in one build and failed in another build at the same time ).
The result is, nobody on your team can see which of your tests pass or fail unless they open Test Manager, which they probably don’t have a license for (unless they are testers).