blocks|key|2926224|text|我想您正在使用C#单元测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2926225|2926226|在“部署到暂存”之前添加了新的阶段“集成测试”，|ordered-list-item|2926227|添加了安装VSTest平台的任务。它将被缓存在代理文件夹中。|2926228|2926229|https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/vstest-platform-tool-installer?view=azure-devops|offset|length|2926230|2926231|为您的测试项目添加了适当的单元测试适配器NuGet包，以便VSTest平台能够在dll程序集中找到单元测试，例如对于NUnit测试，它将是"NUnit+3测试适配器“。|2926232|2926233|(+a)测试文件->，例如"***IntegrationTests.dll“|2926234|b)“由工具安装程序安装”的测试平台版本->|2926235|https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/test/vstest?view=azure-devops|2926236|VSTest任务返回的所有测试结果都将与Azure+DevOps服务集成。|2926237|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|0|0|0|38|0|0|0|0|0|0|0|0|2K|1|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|18|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|19|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1B|8|@]|9|@$K|1C|L|1D|1|1E]]|A|$]]|$1|M|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|1G|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1I|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1J|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1K|8|@]|9|@$K|1L|L|1M|1|1N]]|A|$]]|$1|W|3|X|5|6|7|1O|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|J]]|15|$5|11|12|13|A|$14|V]]]]

I suppose you are using C# unit tests.

<ol>
<li>Add new stage "Integration tests" right before stage "Deployment to Staging".</li>
<li>Add task installing VSTest Platform. It will be cached in agent folder.</li>
</ol>

<a href="https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/vstest-platform-tool-installer?view=azure-devops" rel="nofollow noreferrer">https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/vstest-platform-tool-installer?view=azure-devops</a>

<ol start="3">
<li>Add to your tests projects proper unit tests adapter NuGet package, so that VSTest Platform will be able to find unit tests in dll assemblies, for example for NUnit tests it will be "NUnit 3 Test Adapter".</li>
<li>Add VSTest task specyfing:</li>
</ol>

a) Test files -> for example "***IntegrationTests.dll"

b) Test platform version -> "Installed by Tools Installer"

<a href="https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/test/vstest?view=azure-devops" rel="nofollow noreferrer">https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/test/vstest?view=azure-devops</a>

All test results returned by VSTest task will be integrated with Azure DevOps services.

blocks|key|2926377|text|为了在发布管道中运行集成测试。您应该将测试项目或测试程序集dll文件包含在生成管道中发布的工件中。这样，集成测试项目就可以被发布管道中的测试任务访问。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2926378|将您的测试文件包含在工件中。您可以在构建管道中添加第二个发布构建构件任务。指定路径将发布到测试文件的位置。下面的例子。|offset|length|style|BOLD|2926379|我添加了另一个发布构建工件任务，以发布运行测试所需的所有测试文件。|2926380|​|2926381|📷|atomic|2926382|2926383|然后，我指定了将字段发布到包含所有测试文件的文件夹的路径。|2926384|2926385|2926386|2926387|在构建管道完成后。您将看到Test文件夹被添加到构建工件中，并发布到azure管道服务器。|2926388|2926389|2926390|2926391|现在，您可以通过在发布管道中添加VsTest任务或其他测试任务，在发布管道中运行测试。发布管道将将您的工件下载到文件夹$(System.DefaultWorkingDirectory)(例如。C:\agent_work\r1\a)。|CODE|2926392|对于上面的例子，您将在文件夹$(System.DefaultWorkingDirectory)\artifact_alias\Test中找到测试文件，并在$(System.DefaultWorkingDirectory)\artifact_alias\drop中找到要部署的构件。|2926393|然后，您可以像@Kontekst所提到的那样，在部署阶段之前创建一个具有vstest任务的新阶段，或者在部署任务之前在部署阶段的顶部添加最困难的任务。|2926394|2926395|2926396|2926397|在上面的屏幕截图中，我在Azure部署任务之前添加了Vstest任务，并将搜索文件夹指向测试文件所在的Test文件夹。|2926398|更新：|2926399|您可以在下面的屏幕截图中找到工件--别名。|2926400|2926401|2926402|2926403|其主要思想是在构建管道中的工件中发布测试文件，然后在发布管道中添加测试任务以运行测试。|2926404|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/3da3d407f0b24abb404b55f2332bbce0.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/4ed0d2aec0a2b1b5d6c4e805d2fc53dd.png|2|https://developer.qcloudimg.com/http-save/yehe-900000/8c8e1369a7f5b85f7c1fb543615c7de0.png|3|https://developer.qcloudimg.com/http-save/yehe-900000/e0418b148c19cb16d151ab2974a6eb6e.png|4|https://developer.qcloudimg.com/http-save/yehe-900000/dbd510f3dae376aca0da3472906760a8.png^0|0|I|4|S|6|13|3|0|0|0|0|1|0|0|0|8|I|0|0|0|1|1|0|0|0|0|0|1|2|0|0|1N|X|0|E|1H|25|1H|0|0|0|0|1|3|0|0|11|5|0|0|0|0|0|1|4|0|0|0^^$0|@$1|2|3|4|5|6|7|21|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|22|8|@$D|23|E|24|F|G]|$D|25|E|26|F|G]|$D|27|E|28|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|29|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|2A|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|2B|8|@]|9|@$D|2C|E|2D|1|2E]]|A|$]]|$1|O|3|K|5|6|7|2F|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|2G|8|@$D|2H|E|2I|F|G]]|9|@]|A|$]]|$1|R|3|K|5|6|7|2J|8|@]|9|@]|A|$]]|$1|S|3|M|5|N|7|2K|8|@]|9|@$D|2L|E|2M|1|2N]]|A|$]]|$1|T|3|K|5|6|7|2O|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|2P|8|@]|9|@]|A|$]]|$1|W|3|K|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|X|3|M|5|N|7|2R|8|@]|9|@$D|2S|E|2T|1|2U]]|A|$]]|$1|Y|3|K|5|6|7|2V|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|2W|8|@$D|2X|E|2Y|F|11]]|9|@]|A|$]]|$1|12|3|13|5|6|7|2Z|8|@$D|30|E|31|F|11]|$D|32|E|33|F|11]]|9|@]|A|$]]|$1|14|3|15|5|6|7|34|8|@]|9|@]|A|$]]|$1|16|3|K|5|6|7|35|8|@]|9|@]|A|$]]|$1|17|3|M|5|N|7|36|8|@]|9|@$D|37|E|38|1|39]]|A|$]]|$1|18|3|K|5|6|7|3A|8|@]|9|@]|A|$]]|$1|19|3|1A|5|6|7|3B|8|@$D|3C|E|3D|F|G]]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|3E|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|3F|8|@]|9|@]|A|$]]|$1|1F|3|K|5|6|7|3G|8|@]|9|@]|A|$]]|$1|1G|3|M|5|N|7|3H|8|@]|9|@$D|3I|E|3J|1|3K]]|A|$]]|$1|1H|3|K|5|6|7|3L|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|3M|8|@]|9|@]|A|$]]|$1|1K|3|-4|5|6|7|3N|8|@]|9|@]|A|$]]]|1L|$1M|$5|1N|1O|1P|A|$1Q|1R|1S|-4]]|1T|$5|1N|1O|1P|A|$1Q|1U|1S|-4]]|1V|$5|1N|1O|1P|A|$1Q|1W|1S|-4]]|1X|$5|1N|1O|1P|A|$1Q|1Y|1S|-4]]|1Z|$5|1N|1O|1P|A|$1Q|20|1S|-4]]]]

In order to run Integration Tests in your release pipeline. You should include your Test projects or test assembly dll files in the artifacts published in your build pipeline. So that your Integration test projects are accessible to the test tasks in your release pipeline.
To Include your test files in the artifacts. You can add a second publish build artifacts task in your Build Pipeline. Specify Path to publish to the location of your test files. Fore below example.
I add a another publish build artifacts task to publish all the test files that needed to run the tests.
<a href="https://i.stack.imgur.com/J9FYs.png" rel="noreferrer"><img src="https://i.stack.imgur.com/J9FYs.png" alt="enter image description here" /></a>
Then I specify the Path to publish field to folder that contains all the test files.
<a href="https://i.stack.imgur.com/MKA8j.png" rel="noreferrer"><img src="https://i.stack.imgur.com/MKA8j.png" alt="enter image description here" /></a>
After the build pipeline completed. You will see the Test folder being added to the build artifacts and published to the azure devops pipeline server.
<a href="https://i.stack.imgur.com/P12ec.png" rel="noreferrer"><img src="https://i.stack.imgur.com/P12ec.png" alt="enter image description here" /></a>
Now you can run your tests in your release pipeline by adding the VsTest task or other test tasks in your release pipeline. The release pipeline will download your artifacts to
folder <code>$(System.DefaultWorkingDirectory)</code>(eg. C:\agent_work\r1\a).
For above example you will find the test files in folder <code>$(System.DefaultWorkingDirectory)\artifact_alias\Test</code> and the artifacts to be deployed in <code>$(System.DefaultWorkingDirectory)\artifact_alias\drop</code>.
Then you can either create a new stage with vstest task before deployment stage as @Kontekst mentioned, or just add the vstest task on the top of your deployment stage before your deployment task.
<a href="https://i.stack.imgur.com/bGGmV.png" rel="noreferrer"><img src="https://i.stack.imgur.com/bGGmV.png" alt="enter image description here" /></a>
In above screenshot I add the Vstest task before the Azure deployment task and point the Search folder to the Test folder where the test files reside.
Update:
You can find the artifacts-alias in the field shown in below screenshot.
<a href="https://i.stack.imgur.com/gtkRj.png" rel="noreferrer"><img src="https://i.stack.imgur.com/gtkRj.png" alt="enter image description here" /></a>
The main idea is to publish the test files in the artifacts in build pipeline and then add the test tasks in the release pipeline to run the tests.

blocks|key|1245524|text|我喜欢Levi+Lu-MSFT和Kontekst的两个答案！|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1245525|我的团队过去就是这样做的，它完成了任务。|1245526|然而，如果您想要更多的“爱好者”报告，如果像我一样，您正在寻找微软专门为集成测试或自动化测试提供的现成功能，那么Azure+DevOps的测试计划功能可能就是您所要寻找的。|style|BOLD|1245527|测试计划似乎确实满足了实际的web自动化测试，但您基本上可以运行任何可以安装在发布管道中的测试。|1245528|它与Visual测试管理器集成得很好。|1245529|下面是指向文档的链接：https://learn.microsoft.com/en-us/azure/devops/test/run-automated-tests-from-test-hub?view=azure-devops|1245530|下面是一些屏幕截图，以防链接在将来失败：|1245531|​|1245532|📷|atomic|1245533|1245534|1245535|1245536|1245537|1245538|1245539|1245540|1245541|1245542|1245543|1245544|1245545|1245546|1245547|1245548|1245549|1245550|1245551|1245552|1245553|1245554|1245555|1245556|1245557|1245558|1245559|1245560|1245561|1245562|1245563|1245564|1245565|1245566|1245567|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/users/11882186/levi-lu-msft|1|https://stackoverflow.com/users/6334351/kontekst|2|https://learn.microsoft.com/en-us/azure/devops/test/run-automated-tests-from-test-hub?view=azure-devops|3|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/e15f4492344790adf07c00d3ff84a1de.png|imageAlt|4|https://developer.qcloudimg.com/http-save/yehe-900000/29dd79eab6868340714da4002a940449.png|5|https://developer.qcloudimg.com/http-save/yehe-900000/676500e92dc38c1b481bddb1bfbe46eb.png|6|https://developer.qcloudimg.com/http-save/yehe-900000/2175c043f44ab0c1e370ee91b5b38c79.png|7|https://developer.qcloudimg.com/http-save/yehe-900000/7562e9cf3ee2b55cc235e17297d5fdff.png|8|https://developer.qcloudimg.com/http-save/yehe-900000/c8dfe23cd0bb961fb9588599c3f7e472.png|9|https://developer.qcloudimg.com/http-save/yehe-900000/64bcb45250f5853aa994d3a780439672.png|10|https://developer.qcloudimg.com/http-save/yehe-900000/a5dacaa05785e87e22f2fcd3f84a8071.png|11|https://developer.qcloudimg.com/http-save/yehe-900000/2981a437ef3412e5032f8e28e3b5f2ad.png|12|https://developer.qcloudimg.com/http-save/yehe-900000/c024fcaba46be268e461f891dad10941.png|13|https://developer.qcloudimg.com/http-save/yehe-900000/53bfb6e65f18fd737405775ac6e60686.png|14|https://developer.qcloudimg.com/http-save/yehe-900000/f4e57106d66095bd060c93e7990f1dcf.png^0|3|C|0|G|8|1|0|0|1K|H|0|0|0|B|2V|2|0|0|0|0|1|3|0|0|0|0|1|4|0|0|0|0|1|5|0|0|0|0|1|6|0|0|0|0|1|7|0|0|0|0|1|8|0|0|0|0|1|9|0|0|0|0|1|A|0|0|0|0|1|B|0|0|0|0|1|C|0|0|0|0|1|D|0|0|0|0|1|E|0|0^^$0|@$1|2|3|4|5|6|7|2Y|8|@]|9|@$A|2Z|B|30|1|31]|$A|32|B|33|1|34]]|C|$]]|$1|D|3|E|5|6|7|35|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|36|8|@$A|37|B|38|H|I]]|9|@]|C|$]]|$1|J|3|K|5|6|7|39|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|3A|8|@]|9|@]|C|$]]|$1|N|3|O|5|6|7|3B|8|@]|9|@$A|3C|B|3D|1|3E]]|C|$]]|$1|P|3|Q|5|6|7|3F|8|@]|9|@]|C|$]]|$1|R|3|S|5|6|7|3G|8|@]|9|@]|C|$]]|$1|T|3|U|5|V|7|3H|8|@]|9|@$A|3I|B|3J|1|3K]]|C|$]]|$1|W|3|S|5|6|7|3L|8|@]|9|@]|C|$]]|$1|X|3|S|5|6|7|3M|8|@]|9|@]|C|$]]|$1|Y|3|U|5|V|7|3N|8|@]|9|@$A|3O|B|3P|1|3Q]]|C|$]]|$1|Z|3|S|5|6|7|3R|8|@]|9|@]|C|$]]|$1|10|3|S|5|6|7|3S|8|@]|9|@]|C|$]]|$1|11|3|U|5|V|7|3T|8|@]|9|@$A|3U|B|3V|1|3W]]|C|$]]|$1|12|3|S|5|6|7|3X|8|@]|9|@]|C|$]]|$1|13|3|S|5|6|7|3Y|8|@]|9|@]|C|$]]|$1|14|3|U|5|V|7|3Z|8|@]|9|@$A|40|B|41|1|42]]|C|$]]|$1|15|3|S|5|6|7|43|8|@]|9|@]|C|$]]|$1|16|3|S|5|6|7|44|8|@]|9|@]|C|$]]|$1|17|3|U|5|V|7|45|8|@]|9|@$A|46|B|47|1|48]]|C|$]]|$1|18|3|S|5|6|7|49|8|@]|9|@]|C|$]]|$1|19|3|S|5|6|7|4A|8|@]|9|@]|C|$]]|$1|1A|3|U|5|V|7|4B|8|@]|9|@$A|4C|B|4D|1|4E]]|C|$]]|$1|1B|3|S|5|6|7|4F|8|@]|9|@]|C|$]]|$1|1C|3|S|5|6|7|4G|8|@]|9|@]|C|$]]|$1|1D|3|U|5|V|7|4H|8|@]|9|@$A|4I|B|4J|1|4K]]|C|$]]|$1|1E|3|S|5|6|7|4L|8|@]|9|@]|C|$]]|$1|1F|3|S|5|6|7|4M|8|@]|9|@]|C|$]]|$1|1G|3|U|5|V|7|4N|8|@]|9|@$A|4O|B|4P|1|4Q]]|C|$]]|$1|1H|3|S|5|6|7|4R|8|@]|9|@]|C|$]]|$1|1I|3|S|5|6|7|4S|8|@]|9|@]|C|$]]|$1|1J|3|U|5|V|7|4T|8|@]|9|@$A|4U|B|4V|1|4W]]|C|$]]|$1|1K|3|S|5|6|7|4X|8|@]|9|@]|C|$]]|$1|1L|3|S|5|6|7|4Y|8|@]|9|@]|C|$]]|$1|1M|3|U|5|V|7|4Z|8|@]|9|@$A|50|B|51|1|52]]|C|$]]|$1|1N|3|S|5|6|7|53|8|@]|9|@]|C|$]]|$1|1O|3|S|5|6|7|54|8|@]|9|@]|C|$]]|$1|1P|3|U|5|V|7|55|8|@]|9|@$A|56|B|57|1|58]]|C|$]]|$1|1Q|3|S|5|6|7|59|8|@]|9|@]|C|$]]|$1|1R|3|S|5|6|7|5A|8|@]|9|@]|C|$]]|$1|1S|3|U|5|V|7|5B|8|@]|9|@$A|5C|B|5D|1|5E]]|C|$]]|$1|1T|3|S|5|6|7|5F|8|@]|9|@]|C|$]]|$1|1U|3|-4|5|6|7|5G|8|@]|9|@]|C|$]]]|1V|$1W|$5|1X|1Y|1Z|C|$20|21]]|22|$5|1X|1Y|1Z|C|$20|23]]|24|$5|1X|1Y|1Z|C|$20|25]]|26|$5|27|1Y|28|C|$29|2A|2B|-4]]|2C|$5|27|1Y|28|C|$29|2D|2B|-4]]|2E|$5|27|1Y|28|C|$29|2F|2B|-4]]|2G|$5|27|1Y|28|C|$29|2H|2B|-4]]|2I|$5|27|1Y|28|C|$29|2J|2B|-4]]|2K|$5|27|1Y|28|C|$29|2L|2B|-4]]|2M|$5|27|1Y|28|C|$29|2N|2B|-4]]|2O|$5|27|1Y|28|C|$29|2P|2B|-4]]|2Q|$5|27|1Y|28|C|$29|2R|2B|-4]]|2S|$5|27|1Y|28|C|$29|2T|2B|-4]]|2U|$5|27|1Y|28|C|$29|2V|2B|-4]]|2W|$5|27|1Y|28|C|$29|2X|2B|-4]]]]

I Love both answers by <a href="https://stackoverflow.com/users/11882186/levi-lu-msft">Levi Lu-MSFT</a> and <a href="https://stackoverflow.com/users/6334351/kontekst">Kontekst</a>!
My team used to do it like that and it got the job done.
However if you'd like more &quot;fancier&quot; reporting and if like me, you were looking for something out of the box that Microsoft was offering specifically for integration tests or automated tests then Azure DevOps' Test Plan feature might be what you're looking for.
Test Plans really seem to be catering for actual web automated tests but you can basically run any tests that you can fit in a release pipeline.
It integrates well with Visual Studio Test Manager.
Here's the link to the documentation: <a href="https://learn.microsoft.com/en-us/azure/devops/test/run-automated-tests-from-test-hub?view=azure-devops" rel="nofollow noreferrer">https://learn.microsoft.com/en-us/azure/devops/test/run-automated-tests-from-test-hub?view=azure-devops</a>
And here's some screenshots in case the link fails in the future:
<a href="https://i.stack.imgur.com/ITV6a.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ITV6a.png" alt="Test Plan Settings" /></a>
<a href="https://i.stack.imgur.com/KIW5Z.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/KIW5Z.png" alt="Build Definition" /></a>
<a href="https://i.stack.imgur.com/2NCHD.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/2NCHD.png" alt="Create new Release Pipeline" /></a>
<a href="https://i.stack.imgur.com/CcG5t.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/CcG5t.png" alt="Choose latest version" /></a>
<a href="https://i.stack.imgur.com/uO9c5.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/uO9c5.png" alt="Choose Test Run option" /></a>
<a href="https://i.stack.imgur.com/R6KKV.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/R6KKV.png" alt="Test Platform Version" /></a>
<a href="https://i.stack.imgur.com/DTUAK.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/DTUAK.png" alt=".runsettings file" /></a>
<a href="https://i.stack.imgur.com/WgDmo.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/WgDmo.png" alt="Correct agent pool" /></a>
<a href="https://i.stack.imgur.com/pyZ6p.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/pyZ6p.png" alt="Add artefact" /></a>
<a href="https://i.stack.imgur.com/RItYX.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/RItYX.png" alt="Verify settings" /></a>
<a href="https://i.stack.imgur.com/XxiPc.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/XxiPc.png" alt="Run tests" /></a>
<a href="https://i.stack.imgur.com/xurPL.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/xurPL.png" alt="Reporting" /></a>

I have a staged release pipeline that deploys to Development and then to Staging.

I want my Integration Test project to run during release pipeline only before deployment to staging. How do I do that? is there a specific test task that I will be able to hook into before the staging deployment? like a pre-deploy task or something?

Azure Devops: How to add automated integration test during release pipeline

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个分阶段的发布管道，可以部署到Development，然后再部署到分阶段。我希望只在部署到暂存之前在发布管道期间运行Integration项目。我该怎么做？在分阶段部署之前，是否有特定的测试任务可以挂接？比如部署前的任务什么的？

问Azure Devops:如何在发布管道中添加自动集成测试
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Azure Devops:如何在发布管道中添加自动集成测试EN