Is there some way of discovering which Test Plans and/or Test Suites an individual Test Case has been used in?
In an ideal world, I'd also like to see all the previous outcomes for a particular Test Case. For example, did it fail for a previous release?
.
.
.
I need to be able to start with the Test Case outside of the TestPlans screen. I only have a Test Case number and don't know any of the Test Plans or Suites it's been put into. We have a large number of Test Plans and I can't look in each one individually.
Further update:
How to determine which Plans and Suites an individual Test Case belongs to in TestPlans for AzureDevOps
You could select a test case, then click show/hide details pane. The Associated test suites pane shows you any test suite for any test plan that contains this test case. This includes all projects:
Then, we can view the test suites details in the test plan:
Check the FAQs for manual testing for some details.
Update:
Update2:
Help this helps.
Related
We have some generic test cases in Azure DevOps that are included in multiple test suites. When you run a test case for a web app, the test runner window displays the test case ID and name but not the test suite name. Our client is finding this is leading to some confusion as to what is actually being tested. is there a way to display the test suite name as well as the test case name? I've just discovered that you can use parameters in a test case so I'm about to investigate that, but I think that it may apply only to steps and not the title.
For the record, I have decided to use configurations for this. It's more of a workaround than a solution, because it means creating lots of configurations and assigning them to test suites and also that configurations can't be used for other purposes.
I have manual test plan in Azure DevOps with tree of suites that correspond to different functions in my app. Let's say it looks like this:
Now, I need to have one place where I can review tests results from whole test plan ran for particular build. Like acceptance tests.
There's no way to run multiple suites in one run, I guess. Didn't find such possibility, though. Tests ran suite by suite produce multiple testruns, which is understandable.
What I want to achieve is one link to all test results for specific build which I can provide further to PM.
I need to clone certain Test Suites from one test plan to another.
A test plan is made up of test suites and those test suites are made up of test cases.
So I would like to take a test Suite Id and clone/copy it over to a new test plan.
We are using Azure Dev Ops online.
Is this possible or am I looking at it via the wrong way?
This was something I noticed when upgrading from using MTM for test case management. It seems like this kind of option was missing. I made a developer community post asking for clarity on whether this was a gap.
Current Response:
Thank you for your feedback!
According to your description , I suggest you install Test Case Explorer extension and then you can access to Test Case -> Pivot by Test plan -> click “Clone test plan”, set Area path and Iteration path, then Clone.
In TFS Test Hub, I have a reference test plan in which some hundred of test cases are ordered and sorted in a hierarchy of folders:
- FrontOffice
-- UserManagement
--- TestCase 1234
--- TestCase 5678
- BackOffice
-- etc.
When a new iteration has to be tested, I have two choices:
1- Add existing test cases in a new Test Plan, which is good, but make me lose the folder Hierarchy
2- Clone the reference test plan, which preserves the folders, but makes clones of the test cases
In this last case, the link with the requirement is second order:
Requirement --TestedBy -> ReferenceTestCase --Cloned-> ThisIterationTestCase
Option #1 is good for reporting, but tedious for execution
Option #2 is good for execution, but makes it impossible to query test results bounded to a requirement
Do you guys have any advice regarding this situation?
For your requirement, you can create test suites programmatically through REST API or client API (the structure can be defined in a JSON or xml file):
Create a test suite
The Test Management API – Part 2: Creating & Modifying Test Plans
Currently our Jenkins server only displays a history/graph for the overall number of passed/skipped/failed tests - I'm assuming that's the behavior out of the box.
If you select a single test, you'll get information for how long the test was failing (assuming it did fail).
However, we'd like to see is a history for that single test across the different builds to identify whether the test has been failing in the past (and when) even though it just passed. If you find a build where it failed, you could click on it, and investigate what might have caused the failure; if it passes again, you could check whether something actually fixed the test, or whether it was failing randomly all along.
Is this something that can be done somehow through the config, or do we need an additional plugin for this? If yes, which one?
Not sure if this makes much difference, but we're using Java (Maven) & TestNG (Surefire).
Both the TestNG plugin and the JUnit plugin will actually display history of the test results.
You just need to pick a given result and then:
For JUnit click on "History" on the left side, and
For TestNG click you will see the history in the graph above the result. You can just click on the bars in the bars to see the older results, and also if you click closer to the edge, the scope of the test results will adjust
The Test Results Analyzer plugin does the job for me. There appears to be other suitable plugins out there as well.
https://wiki.jenkins-ci.org/display/JENKINS/Test+Results+Analyzer+Plugin
Does the Static Code Analysis plugin help?