Reputation: 521
I would like to have manual test as a required step in a release pipeline, much like automated tests in build.
Tried to find if this was possible in Azure Devops
I would expect manual testing as a required part of a release.
Upvotes: 0
Views: 1125
Reputation: 11
if we are using TFS 2010 for release management we can create the test case in Microsoft test manager 2010 and at the time of production release we can make a mandatory check to validate the test cases. we will write the test case using Microsoft test manager and will link this test case with TFS Win no. once we move the source code from UAT to production we will make a mandatory check to validate the test case created in Microsoft test manager
Upvotes: 0
Reputation: 19361
Can manual tests be incorporated in a pipeline as a required step?
For this issue , I am afraid it is currently not supported in azure devops. Compared with manual testing, integrating automatic testing in the pipeline is more in line with the CI/CD concept. Adding a manual test is more of a requirement. In addition, the default timeout for the pipeline is 60min. If the wait time for the manual test times out, it may cause a failure.
So we can't directly incorporate manual tests in pipelines. The workaround provided by Nima is an indirect way.
If you really need this feature,you could submit a feature request in our Develop Community site. Our PM and product team will kindly review your suggestion.
Upvotes: 2
Reputation: 509
You can add a new stage with approval right after the draft deploy (dev environment). In the first step, deploy your app in a server. The the specific user can do a manual test, then approve the deployed artifact as a release condidate. Finally, your production step will run after the user confirmation.
Upvotes: 1