Can anyone please explain me about the run id in TFS since currently I am using one of the TFS API to get the testcase outcome using this runid and the thing is I don't have that much knowledge regarding runid and all.
So please tell me what does exactly runid mean? how it related to test case? Does TFS generate new runid if we update something on testcase?
In the Test Case you are configure a case - Steps with action and Excepted result.
When you want to check the case, you need to "run" the test case, after it you will have run id.
How do you run the cases and see the test runs history? click on the "Test" tab, and then choose on "Test Plans", now you will see the Test Suits with the Test Cases. you can choose a Test Case and click "Run":
After you will complete the run you can do the "Runs" tab and see the history and the "Run ID":
So, for conclusion, when you test the Test Case (it can be multiple times) you get a new Run ID (exist under the "Runs" tab).
Related
I have two test plans with a lot of tests. I want to select all in one test plan, and add these tests to another existing test plan, leaving the second with all the original tests plus the ones appended from the first.
When I select all the tests in the first test plan, there are options to create a test execution, a test set, but nothing to add to test plan (which is what you see if you are in the testing board)
I don't want to have to open each test individually and add it to the second test plan, as I already have them in a list in the first one. TIA.
You have two options to do what you are searching for, that is adding tests from one Test Plan to another:
Create a Filter that will have all the tests that you want to add and then add those using the Add Tests option like below:
Add those tests to a Test Set and then add the Tests to the Test Plan through the Test Set, like below:
Thanks, thats done it for me! :)
I'm using TFS 2015 to run automated regression tests nightly. There are over 100 tests in the suite but each night 1 of them, usually the same one, shows up with the outcome "None".
If I look at the test log I see that the test does not fail. If I remove this test from the suite then on the next run the test above that one, in code, will show as "None" but it also passes.
What could cause this and how do I determine the cause?
We upload results after finishing execution of the set of tests given
to an agent. From #1410 it sounded like all your tests are
currently going to 1 machine, which would mean all results are
uploaded only at the end. Also, the Test Results tab in Build Summary
(image you pasted above) only shows results once the run is complete.
You can go to the Runs tab in the Test Hub to see test results as and
when they are available, even for in progress runs (image below)
Source Link
So in other words, you have to wait for the full completion of the process, the root cause of the status none issue maybe either your enitre test process haven't finished yet or something special cause the process not finished.
I am using VSTS to maintain our test cases.
I have created a test suite named Login Tests inside test plan foundation, which contains all the scenarios for login validation.
I want to add all existing test cases which are in Login Tests to my new test plan. Currently, I am manually copying and pasting the IDs in the search query,but is there any way where I can get all the test cases inside a suite.
No, there is no way to do as you describe.
However there is an easy workflow change that will allow you to do this. You have some manual work to get there, but once there things will be better. You should go through all of your Test Cases in the manual Suite and tag them with "tests-login".
Once done you can easily create Query Based suites anywhere with the correct list and control the list using the Tag.
Right Click the suit in the VSTS Test manager folder and Export to email you can select multiple suit and past in excel from email
How to copy and create test case from JIRA. Currently I am creating test case as Create-->Project(XXX)-->Issue Type(Test) .In this way I have created test case with 8 test steps.Now I would need to create new test case by copying the previous test steps.How can I do?
You should be able to clone the issue. This is a menu item under the 'More' menu in the issue details screen.
If you can't see More->Clone it is possible your user does not have sufficient privileges to do this operation.
Is there a way to mark a fitnesse test such that it will not be run as part of a suite, but it can still be run manually?
We have our FitNesse tests running as part of our continuous integration, so new tests that are not yet implemented cause the build to fail. We'd like a way to allow our testers and BAs to be able to add new tests that will fail while still continuing to validate the existing tests as part of continuous integration.
Any suggestions?
The best way to do this is with suite tags. You can mark tests with a tag from the properties page and then you can filter for the or filter to exclude them.
In this case I would exclude with "NotOnCI" tag. Then add the following argument to the URL:
ExcludeSuiteFilter=NotOnCI
This might look like this then as the full URL:
Http://localhost:8080/FrontPage?test&ExcludeSuiteFilter=NotOnCI
You can select multiple tags by splitting with commas, but they act as "or",Not "and".
Check the FitNesse user guide for more details. http://fitnesse.org/FitNesse.UserGuide.TestSuites.TagsAndFilters
Would it make sense to have multiple Suites, one for regression tests that should always pass, and another one for the tests that are not yet implemented?
Testers and BAs can add tests/suites to the latter suite and the CI server only runs tests in the former suite.
Once a developer believes he has implemented the behavior they can move the test/suite relating to that functionality to the 'regression' suite so that it will be checked in continuous integration.
This might make the status of a test/suite a bit more explicit/obvious than just having a tag. It would also provide a clear handover from development to test/BA to indicate the implementation is finished.
If you just want to have a test/suite not run during an overall run of a suite that contains the particular test/suite you could also just tick 'Skip (Recursive)' in the properties page of that test/suite (below 'Page Type').