If I am editing a test case using Microsoft Test Manager (2017), I can select a set of test steps and then copy and paste them into the same or a different test case.
Is it possible to do the same thing when editing the test case from the browser (TFS 2017)? If so, how?
There is an option "Edit Selected test cases in grid view" in the test case context menu, you can copy/paste test steps with the feature in browser.
But unfortunately the feature is missed in TFS 2017 Update1, So you cannot copy/paste the test steps by editing the test case from the browser if you are using TFS 2017 Update1.
As a workaround you can create a test case query, then open the query in Excel, then copy/paste test steps cross test cases, then publish the update.
Edit Selected test cases in grid view option is back in the latest TFS 2017 Update2. So, you can also upgrade to the latest TFS 2017 Update2, then edit case within the grid view.
Related
I have the following problem where Associated Automation not showing tests.
The project has been checked in and the Unit Tests show up fine on Test Explorer
When I query and search for a Test Case in TFS then attempt to link a Unit Test to the Test case via the associate button, nothing appears in the Choose Test window.
Any help please?
When using MS Test Manager 2013 there does not seem to be any way of adding/editing tags on a test case. I can however select tags as a column to be displayed in for test cases in MTM.
If I open the test case work item in the TFS web portal, I can add/edit tags on the test case there.
Am I missing something? Is there any way to add tags in MTM without having to flip over to web access every time.
Make sure you update your Test Manager / Visual Studio installation to the latest Visual Studio Update, that should enable the Tags field on your work items.
If I remember correctly, your TFS server also needs to have at least TFS 2013 update 2 installed, but as Microsoft only supports the latest released update, I'd recommend to update to TFS 2013 Update 4.
I converted a project with nunit tests, so that it had mstests instead. It compiles, and when I right click on the project, I can select "run unit tests." It works, and the tests execute successfully.
However, I cannot see my tests in either the "Test List Editor" or the "Test View." I've tried:
selecting the "refresh" button in both those lists
rebuilding the solution
re-starting visual studio
Activated background discovery (I do have VS 2010 SP1, and resharper)
None of these, alone or in combination, has worked. What else can be tried, to force Visual Studio fully to recognize these tests?
The answer, I found, is that I must convert a class library to an MsTest project.
Also make sure that your test class is public, I spent almost one day trying to figure out why the MS test frame can't discover my test until I modified the access modifier from the default to public
I am running Windows 7 Ultimate and Visual Studio 2010 Ultimate. Somehow, in some way, the option of creating new Coded UI tests (right click on test project, select Add New Item, select Coded UI Test) disappeared from VS 2010.
Has anyone ever heard of such a thing? If so, how did you fix it?
Everything in Visual Studio related to Coded UI Tests is context specific. For example, you can only find the Coded UI Test Builder link when your cursor is in a class marked [CodedUITest]. Create a new "Test Project" in your solution and see if the Coded UI Test comes back. If so, something happened to your other project file.
I have a Visual Studio 2008 solution that contains around 30 projects. Some of these are web services / WCF services / ASP.NET MVC applications.
When I run all unit tests (Ctr+R, A) it insists on spinning up all the Development Servers for these various projects. This means that it takes far too long to run the tests and, actually, none of my unit tests require these frameworks.
So, how do I stop Visual Studio doing this?
Click on the projects in your solution and bring up the properties window (F4).
Change Always start when debugging to false.
If you're running the tests, not debugging, then the "Always start when debugging" setting will have no effect.
Instead, have a look at the test settings that you're using to run the tests. (Find which settings you're using by going Test > Select Active Test Settings. You can then edit the test settings by going Test > Edit Test Settings and selecting your active test settings)
I have found the following test settings can force the ASP.NET development server to start up, although there could be more!
Non-default test host: In the edit test settings window, choose the "Hosts" section. Host type should be set to "Default", not "ASP.NET"
Code Coverage: In the edit test settings window, choose the "Data and Diagnostics" section. Select "Code Coverage" and click "Configure". The development server will start for each service that is selected here for ASP.NET Code Coverage. (Normal code coverage is identified by an icon of a blank page with two gears on top of it. ASP.NET code coverage is identified by an icon of a globe with two pages on top of it.) To change from ASP.NET code coverage to normal code coverage, deselect the ASP.NET code coverage, then choose "Add Assembly...". Browse to the bin folder of your web service project and choose the dll of the web service.