Need guidance to run tests when using CI/CD on VSTS

Hi there, would be great if you could provide additional guidance for testing when using VSTS for CI/CD.

So far I have built the ‘unittest’ container and modified the dockerfile to include: RUN dotnet test --logger "trx;LogFileName=TEST-unittest_results.xml" I can see the tests being run and the file being created BUT how do I know get the file in VSTS and how to stop the build if there are failing tests? I have added the ‘Publish Test Results’ task but it doesn’t find the file. I’m guessing this is because the file is in the container vs the build environment.

I found this but cant seem to get it working (I’m guessing it is because I am using the Linux host).

Is there are more elegant way?

[eiximenis]

Hi. I think there is a better approach:

1. Having a container test that saves the test results to a xml file
2. Add the test container to compose file
3. Create a bind mount for sharing xml results file between container and host (vsts agent)
4. Use “docker-compose run” to run the test container. If test fails, this will make vsts build to fail (note that do not happen using docker-compose up).
5. Use the “publish test results” task to publish test results to vsts. Configure task to run even though previous task fails.

[A bit of spam]: I wrote a blog post in my blog (in spanish) about the topic: https://geeks.ms/etomas/2018/03/07/ejecutar-pruebas-de-tus-contenedores-en-vsts/ It is centered on a simpler case (only one container) but is easily extensible to multi-container solution like eShop.

Anyway @CESARDELATORRE maybe we could create some wiki topic for this issue

[mvelosop]

Closing this issue.

• Included a reference in the roadmap vNet section
• Important tip in Stack Overflow