tcm suites
can clone suites into different team projects within a TFS server. I want to clone an entire suite from our test TFS server to the prod TFS server. This page doesn't say anything about cloning between servers. Is there a way to do it? How?
What you are looking for migrate Test Suite from one TFS to another. If you only need the Test Suite (no include Test Case), you can export the Test Suite work items to Excel in test TFS and import the Excel to the prod TFS.
Or you'll need to use some third party tool to achieve your requirement, like OpsHub Commercial Utility.
After some experiment, the answer is no. You can't clone, copy or migrate an entire Test Suite from one TFS Server to another. The best way so far is to manually create the Test Suite with its tree structure and the Test Cases under them. Well, Too bad!
Related
I have 2 executables, an app and an automation test app who will perform actions on the app. My automation tests are basically NUNIT tests who calls Chrome Web Driver.
Everything is hosted at TFS. In my build definition, i run sanity checks for every PR. I wanted to expand that. The automation tests are divided into many different categories (being Sanity a category). I've been seeing some stuff related to TFS Test Suits, and my idea was to make in a way whenever when someone makes a PR, he could choose some test category to run on that PR using that build. So in a easyer way of sayng, if my PR changes how 'blue buttons work' ill run the 'blue buttons test suit' on my pr.
Would using Test Suits be the best solution for this ? Has any1 done this or have any nice information on how to achieve this ?
Thanks for any responses !! Best regards !
You could be able to use the Visual Studio Test Agent Deploy and Run Functional tests steps in your build definition to run auto tests on build agents.
Associated test methods with test cases in Visual Studio.
Create a build definition to build your project and add the 2 steps I mentioned above. In the Run Functional Test step, select the test suites which contains those test cases in step1.
More details please refer this blog: Executing Automated tests in Build vNext using Test Plan, Test Suites
Today faced a challenge, due to some infrastructure issue our TFS and MTM was down and the whole testing team was sitting idle as they can't access their test scripts. Is there a way that we can export/download test scripts from MTM to local machine (as we do for codebase i.e. local machine copy) so as to avoid this type of problem.
I know this will be a common problem but somehow unable to find a answer to this.
You can export an entire test plan from the web interface and you have the possibility to choose if the test cases with steps are included or not in the export.
You cant export for offline access. You can create static report of all of the test cases and steps in the web access. There is however no easy to get the data back in.
To be honest this is not a common ask as most folks TFS servers do not randomly go offline. As TFS is a production system you should get at least four nines SLA. If you don't then I would recommend that you move your TFS to VSO.
Currently when we clone a test plan in Microsoft Test Manager we need to specify an area path for the cloned test cases. This is bad when we use the area path for TFS Teams or we use it for product area management and the cloned test cases end up having all the same area path.
I have already shared this idea on User Voice, but I would like to know if there is an workaround for this. A clone tool would also be very welcome.
This tool may be exactly what you need: TFS 2013 Tester Power Tool - Bulk Copy Test Cases for Microsoft Test Manager
I'm trying to setup TFS 2010 Lab Management based Automated Testing system and I have a "Test suite" (Created in TFS Test Manager) with following tests:
1) Start and Login
2) Create group
3) Create user and add to the group
These have order specified properly in Testing Center->Plan->(Test suite)->Order column
However, when they are executed (on TFS Lab Management Build) by Test Agent they run out of order: 2nd then 1st and then 3rd.
Is there a way to make Test Agent run these tests in order?
Thanks.
Create an Ordered Test, it's a simple list of which test methods should run and in what order.
I also had the same issue. I solved it by installing VS2010 Service Pack and TFS 2010 Service Pack in both the Test controller machine and Test agent machines. Please go through the following link for more details
http://social.msdn.microsoft.com/Forums/en-US/vsmantest/thread/29ac3c7b-b0cd-40f3-9992-f5f3c2285331
Unfortunately, There's a blog regarding ordering test cases which says:
Please note this only applies to the manual tests but not automated
tests. For automated tests, the order you set here will not be
respected during test execution.
http://blogs.msdn.com/b/vstsqualitytools/archive/2009/11/21/run-your-tests-in-the-order-you-want.aspx
I don't know if it's a new feature but you can create Ordered tests. Just right click on your project in Solution Explorer and choose Add -> Ordered Test. Select you tests in order.
In Test Explorer, run you ordered test.
Details are in the link below but all I had to do is what I'd said above. I am using VS 2015 Enterprise.
https://msdn.microsoft.com/en-us/library/ms182631.aspx
Some background: I am not a tfs guy and I dont know much about build scripts etc.
1 - Is there a way to run tests for every check-in TFS? What I'm dreaming is, if any of the tests is failing then build server rejects the changeset. Is it possible with TFS or should it be some other tool like Hudson, Cruise Control etc? What are the other powerful tools?
2 - Does using such a tool make it possible to run only portion of tests, not all of them (ie only unit tests, not integration tests)?
I am not interested in technical details like how it can be done technically, as it is our tfs team's job. Rather I am after some high level info about the possibilities?
In TFS you have what's called check-in policies. With those in place you could forbid checking-in something without all of the unit tests passing. You could even enforce FxCop rules, etc... but that would be cruel to your developers.
If you already have the Continuous Integration build set up, then change the trigger to Gated Check In, this will do exactly what you want. When a developer tries to commit, TFS will start the build, if the build fails then the check in will be aborted and instead TFS will create a shelveset of the changes.
As for running a portion of the tests, you would probably need to create a test list in your VSMDI that defines the tests you want to run and then configure the build to use that list.