Learn to use Visual Studio, Visual Studio Online, Application Insights and Team Foundation Server to decrease rework, increase transparency into your application and increase the rate at which you can ship high quality software throughout the application lifecycle
As part of the MTM enhancements in the Visual Studio Update 2, we introduced a feature to customize the test result analysis fields like 'Resolution' and 'Failure type'. Different projects may have different reporting needs and this feature lets you do just that. You can customize the values that appear in these fields based on your project requirements, using a simple command. This nice post by Colin Dembovsky talks in detail about this capability.
We also introduced a new test outcome state called 'Not applicable' for marking test results in MTM or the TEST hub. When you are doing your testing, you may come across test cases that are not relevant to your current test pass or they might be referring to areas in your application that are yet to be implemented. In such cases, you do not want to leave theses test cases unmarked, or use some other state to denote this condition as these may get wrongly interpreted. This new 'Not applicable' state lets you deal with these situations.
You can mark a test as 'Not applicable' from the Test->Run tests tab in MTM:
You can also do this from the test runner:
You could access this state from the TEST hub in TFS web access:
This can also be done from the web test runner:
Other enhancements done in VS Update 2:
For the "Not applicable" status to appear do you need to have TFS 2012?
I have VS 2012 Update2 installed but our TFS is still 2010.
@Jean - yes, you need to update both your server and client to get this feature.
Don't release the xbox1 you will be sending alot of xbox gamers to PS4
Can someone introduce me to the Test Servers Manager?
Thank you in advance,
@Raja - are you looking for contacts for "Microsoft Test Manager"? If so, you can reach me at firstname.lastname@example.org
Is it possible to mark only a single step in a TestCase to "Not applicable" - not the whole Test
Hi, how can I set up "Not applicable" status in Test Manager 2013
Does anyone know how it's possible to mark one teststep to N/A?!
"Not applicable" status should be made to apply to test steps. I notice two questions on this have not been responded to
We can pull out the report at test case level. Can we do that at test step level. If yes, please provide the steps to follow.