When to use Microsoft Test Manager?

Question

I'm new to testing and looking into coded ui testing. I noticed that there are two options 1) using the Visual Studio and record the actions from there and then generated the code 2) use the Microsoft Test Manager and do the recording. I'm curious to know what is the advantage of using Microsoft Test Manager? Is there anything that I can't do if I use solely the Visual Studio?

Answer 1

(Disclaimer: I worked on Visual Studio at Microsoft)

Microsoft Test Manager is useful when you're a large organisation and have a team of dedicated testers (non-SDET testers), Test Manager gives you a much simpler environment that requires far less user training and also means testers don't need access to the project source code.

If you're doing SDET work, developing your own automated testing or in a small team then you'll be fine with Visual Studio, but if you're writing manual test cases for QA folk to follow, or automated tests that need babysiting by QA people, then you'll want to use MTM.

Answer 2

Microsoft test manager (mtm) is a good place to organize manual tests. I don't record tests from mtm because it sometimes has trouble identifying controls on a page. To get action recording, I suggest hand coding the tests using coded ui test framework in visual studio and linking them with manual test cases that were created in mtm

Answer 3

the most amazing part in MTM, that

1. you will be able to organize your test and iterations ,

2. it help in writing the bugs depending n the format of test case .

3. make sure you had cover all the required parts using code coverage

4. you will be able to check where the test impact has happen

5. recording test case , but I don't like it, but if you need to automate you can integrate with Selenium