Microsoft Test Manager is primarily a tool for managing manual tests. The MTM test recordings can be exported to CodedUI then modified in Visual Studio, but they are not automated tests and should not be treated as such.
If you have Microsoft Team Foundation Server configured to manage test environment virtual systems, you can configure MTM to run automated ...
If you are a programmer you need Microsoft Visual Studio Enterprise which is $5,999/user/first year and includes Team Foundation Server online access & Microsoft Test Manager stand alone app.
Anyone doing just QA and no programming can use Visual Studio Test Professional which will cost your company less $2,169/user/first year and only includes Team ...
I was able to accomplish this by writing a custom TestClassExtensionAttribute and then calling a custom ITestMethodInvoker from the TestExtensionExecution.
I answered a similar question on SO about this:
I have posted the code on GitHub and am working on cleaning it up a bit:
In my experience, you can't sell new development processes.
The only path I've found which works is to simply start doing it: Only develop with TDD from this point forward. You'll still deliver your code on time, but it'll be more maintainable and have far fewer bugs. You'll feel much less anxiety and be proud of your work.
After a little time, management ...
As I understand it (I'm not that experienced with MSTest/Test Manager yet), without the Lab Management module the way to do this is to install SysInternals to each of your target environments as well as your master/controller environment, then use a batch file that runs the tests.
The basic setup is a batch file to run the tests - you can call MSTest from ...
You've actually got several options here. The key is that Microsoft Test Manager has to integrate with Team Foundation Server: if you can connect your Selenium tests to Team Foundation Server you can use the Associated Automation field in the test case to link your Selenium test code to MTM test cases.
Team Foundation Server plugin for Eclipse: this is an ...
Check out the answer to this question over at StackOverflow.
(From the accepted answer) NUnit has few advantages over MS-Test
Suite attribute - can aggregate tests and execute them separately (useful for large projects with fast and slow tests for example)
Readable Assert method, e.g. Assert.AreEqual(expected, actual) vs Assert.That(actual, Is.EqualTo(...
There are a few ways to do this, one would be:
You could create your template list of test cases in an excel file and import them to TFS using http://tcmimport.codeplex.com/
You can also export an existing list to use with http://exporttfs2excel.codeplex.com/
Another way would be to create copies of the test cases.
Well, I found this link, that helped...I didn't know that my visual studio project that has mstest installed as a package included with it, did not know where the testadapter was located.
had to add /...
If you can open the test in Visual Studio v14.0
Open the test solution and change the reference to the CodedUITestFramework. It should show as a broken reference because you don't have v11.0 installed. Then save and recompile.
If you can't open the test in VS 14.0
Your best option (which may not work) is to edit the test's app.config to include the ...
you do not give closing quotation marks in the second line:
mstest /testcontainer:"C:\Users\tmh\Documents\Visual Studio 2015\Projects\FocusCREAnalytics\FocusCREAnalytics\bin\Debug\FocusCREAnalytics.dll"
This is because test runs are not directly associated to Test Cases.
Each test case is associated with at least one configuration (if you don't assign one, there's a generic default). The pair [Test Case, Test Configuration] forms a Test Point, and each run is associated to the test point.
MTM queries work on Work Items, and can only return data ...
Normally its recommended to keep them outside the application environment itself. In part because the running of the tests will confuse results (for example if you are testing the response time of the system then the load of the test runner will directly skew results)
You can kick off the run on code changes using a build server such as TFS/Jenkins/Bamboo. ...
You can use the TFS SDK to directly insert test results. See https://stackoverflow.com/questions/6505812/how-to-create-a-test-run-and-result-using-the-team-foundation-server-api.
This may or may not be a worthwhile use of your time to implement something like this. TFS is pretty integrated with MSTest and the entire Microsoft infrastructure. While you ...
As far as I know, you can only associate and execute MSTest based test automation to test cases in TFS. You could write a MSTest test method to wrap each of your protractor test cases. Somebody did something similar here for Ranorex tests. Doing that manually would be painful, so I'd recommend automating the MSTest dll creation.
There's also the ...
Adding new column for Test suite depends on version of TFS that you're using. In TFS 2013 Test Suite is a work item like any other, but apparently there's no easy way to get additional information. Comment field (it's 'Description' in TFS, but it looks the same to me) can be accessed via pressing Ctrl+G ("Go to work item" window will appear) and fill in "...
MS has several command line tools that will run tests. There's more information about how to use them and how to choose the tool you use on the MSDN site:
I'd suggest reading the documentation and experimenting with the different tools to decide which of the tools works best for your situation.
This isn't possible without some serious messing around with the TFS API right now.
Part of the problem is that internally test cases are stored as work items where test plans and test results are stored in completely different parts of the system with complex relationship structures. As a result, the built in query engine can't access them.
Found the answer. Agents cannot debug remotely, and while the build I was executing against in the above post was "release" (in one instance), I was still attempting to debug. If I select the test and click "Run" instead, it executes successfully on the remote agent.
Actually not. Microsoft Test Manager is a simple T. management tool which allows you to run a Test case and report a bug into TFS, built on the top of Visual studio. It would be probably possible to plug it in, but usually there is nothing like this.
There are several test frameworks and automated test tools build on the top of visual studio as Ranorex, so ...
You can pause the test run, then save and close. All the attachments you've created to that point will be saved.
When you're ready to come back to the test, you'll need to return to the point you left and located the unfinished run (Test > Analyze Test Runs), then Resume.
You should be able to pick up where you left off.