The organization I am with has transitioned to Azure DevOps for source control and for Sprint Management. I am responsible for investigating moving the organization to Azure DevOps for testing off of another solution. There is one question I have received from multiple people after doing some demonstrations that I have not been able to get an answer on.
What I have been asked if the system can do, is that when a Bug is entered during a Test Execution, for it to automatically have the User Story that the script is related to be set as a parent.
For example:
If I have User Story 123, which has a Tested By relationship to Test Case Test1. Test Case Test1 is in Test Plan ABC, which was created with the Area Path of my team and Iteration of the current Iteration. If I create a Bug while executing Test1 (in a Test Suite in Test Plan ABC), it currently adds the Bug to the current Iteration, but under an Unparented story. We would like to see that bug automatically appear under User Story 123.
Is this possible? Thanks for any information regarding this.
I think you can use Create work item task behind your test task in your build/release pipeline.
In this task, you can set the work item link type and target work item.
And other conditions about the work item.
You can set the Control Options as below.
It means, only when the test task has failed, this task will run.
Hops this will help.
So, for anyone else searching, I was able to resolve my issue.
What ended up being the solution was using the Create Test Suite from Requirement option, within a Test Plan. This is a very useful method for our use, as once the Test Suite is setup, and Test Cases which are created with a Tested By/Test Relationship (User case should show Tested By in the Related Work section, the test case will show a Tests entry to the User story) will automatically be added into the Test Suite. Then, when testing, when you create a new Bug from within a Test Execution, will automatically be created with the User Story as a Parent to the Bug.
Related
We are currently checking the test plan module on our Azure Devops server and I'm facing an issue that the community may help.
According to this once a test run has been marked as failed or blocked there is no way to resume the test once the raised defects have been resolved. You either have to mark the test run as paused (so as to be granted the "resume" option) or reset the whole test to active in which case you loose all your progress and need to start over. Two questions:
This "workaround" works as long as you are careful and save the test run as paused. Otherwise if a failed step exists the run is saved as failed. Once this is done I have found no way of changing it to "paused" so as to get the resume option. Is there a way I'm missing?
In the test list under a specific suite you get the current test run outcome and state of test case. In case of "Paused" you don't have a way to know if the test execution is paused or you are utilizing the aforementioned workaround (e.g. a bug is registered). I cannot see a way that I could enhance the test run with some information that would signal this (there is no wit template I have found) on the grid. So is the standard query module (bringing testcases and associated bugs with state) the only way?
thanks
For the first question, if the test case is on status Failed and you retest the test case, all test steps need to be redone. Also there is no resume-button. This is by design. For now, set the status to Paused can resume the test, but it cannot truly reflect the result. As far as I know, there is no other way.
You could add your request for this feature(For example: when status = Failed/Block, the restore button is enable) on our UserVoice site , which is our main forum for product suggestions.After suggest raised, you can vote and add your comments for this feedback. The product team would provide the updates if they view it.
For the second question, as workaround , you can also add tags to paused test cases for labeling.
In Azure Devops, After creating the Test plan, it's possible to run the tests manually and take screenshots, video, or add a comment during the test run. But when I try to export the Test plan after the execution is completed, it's not possible to export the screenshots, comments or videos as attachments. Is there a way to do this ? We work in regulated Industry and need to provide evidence for the test results.
Please go through below link and each steps:
Link:https://www.azuredevopslabs.com/labs/azuredevops/testmanagement/
Navigate to your team project on Azure DevOps.
Select Test Plans to navigate to the Test Hub. The test hub provides a central place for all test planning, execution, and analysis.
In general, every major milestone in a project should have its own test plan. Within each test plan are test suites, which are collections of test cases (and optionally other test suites) designed to validate a work item, such as a feature implementation or bug fix. Each test case is designed to confirm a specific behaviour and may belong to one or more test suites. The Parts Unlimited project has one test plan, which is under the Parts Unlimited Team and called Parts Unlimited_TestPlan1. Select the Parts Unlimited_TestPlan1 test plan.
Select the suite of tests for the story As a customer, I would like to store my credit card details securely. This suite of tests focuses on that work item, which happens to be a feature. Note that the work item numbers will vary every time you generate demo data for a lab.
On the right side you can see that this test suite has three test cases designed to confirm expected behaviour of the feature implementation. Double-click the Verify that user is allowed to save his credit card detail test case.
This dialog provides all the info you need on this test case. Locate the Related Work panel and note that this test case is linked to the suite it belongs to. Click the work item to navigate to it.
In the test suite, we can see all of the linked work items, which happen to be the test cases.
However, it’s not yet associated with the feature it’s designed to test, which we can link now. Click Add link | Existing item.
Set the Link type to Parent and search for “credit card”.
Select the Feature for Credit Card Purchase.
Click OK.
The parent feature is now associated with the suite that tests it and anyone can navigate between them to view their relationship relative to the other work items involved.
Click Save & Close.
Dismiss the original test case dialog.
For this issue ,if you want to download attachment from test run ,you can go into Tests Plan -> Runs. Then you will be able to click on Tests Runs, select the run you want to download, and simply download the attachment.
You can also export test plans, test suites, and test cases from Test Plans. Select the details that you want in the report. Then email or print this report for review.
You can refer to this case with the similar issue.
Can you explain your questions in more detail? Are you using any tools for writing test plans or taking screenshots? There are various tools for writing test cases.
If you are looking for some test plan/test cases management tools:
Hiptest
TestRail
I've done some searching but can't find an answer to this. In our current Test Case Management System, we have an option to archive Test Cases which are no longer relevant (eg because an API or UI option was removed). The TC still exists, but just cannot be executed in any Test Suites any longer.
However, I cannot find any such option in Azure DevOps ... is there ? The closest I can find is deleting a work item, but that's obviously not what I'm after. I know that other work items (stories, epics, bugs etc) have a defined beginning and end, but TCs tend to stay around as long as they are relevant (for automation/regression testing etc), so I feel they should have a slightly different lifecycle than other work items.
Anybody found a way of doing this in Azure DevOps or found an alternate solution ?
There is no out-of-box features for that. You may try on of these suggestions:
Just add new tag "Deprecated" or "Archive". Add work item tags
Add area path "Archive" and move work items to it. Define area paths
Edit your process template and add new state "Archive" to "Remove" category in the test case work item type. Add a workflow state
I want to link test run results to user story to add more traceability on board for all team members.
I've found that I can add link for New and Existing items, but there I can find only Work item type: Bug, Blocker, Epic, Feature, Test Case, User Story etc.
If I add link to test case, I will see only test case itself (test steps) and can't find any information about this test case in some test suit or test run results.
I've explored VSTS documentation: Link user stories, issues, bugs, and other work items and Linking, traceability, and managing dependencies.
As I understood, there is no such functionality right now in Azure DevOps (VSTS).
As you said, currently there is no such thing in Azure DevOps, but there is a great extension to add the test run results in the test case.
The (free) extension called View Latest Test Result, after you install it you need to modify the process template (to add the results) and then you got this:
On Developer Community I found opened ticket for it:
Need ability to link Test Results back to ANY work item type, especially User Stories
I did up vote, but it seems that for now I can only wait for this feature.
Whenever I try to import a workflow from Dev/Test environment of a versioned repository into Production environment which is also versioned, I get a option where it asks me if I want to Check in or continue without check in. What happens if I do not check in and continue? Will all the objects used in the workflow will not be checked in or is it just the workflow which will not be checked in? I am asking this because, it will be double work if all the objects used will not be checked in including the Workflow, then, I have to go one by one to check in the objects. If I check the check in option for the workflow, after importing the Workflow, the integration service is left blank and when I run it, it is pointing towards the Integration service not mentioned error. For this I generally check out the workflow once I import just to mention the Integration service name. I do not think this is a good practice. Any advices on this will be greatly appreciated.
Thanks
Dhruuv.
Will all the objects used in the workflow will not be checked in or is it just the workflow which will not be checked in?
The objects that will be left in the checked out state are:
the workflow,
the new objects (i.e. they were not present in the Prod repository before the import from Dev/Test),
the modified objects (i.e. they were present in the Prod repository but were overwritten because you chose the Replace option).
I have to go one by one to check in the objects
You don't have to check in every individual object - in Repository Manager open the Versioning menu and choose the Find Checkouts... option. All the checked out objects will be listed - you can select them and check in all of them at once.