-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Report does not load in Azure Dev Ops #37
Comments
Do you use a (multi-stage) YAML pipeline? If so I have noticed the same thing #32 And no, you shouldn't need to publish the report as an artifact. |
I'm getting the same thing in Azure DevOps when using dotnet core 3.1 with dotnet-stryker installed as local tool in the test project. This is my yaml code: - script: dotnet tool restore
workingDirectory: 'tests/domain/Company.Product.Domain.Tests.Unit'
displayName: 'Install dotnet tools for Stryker.CLI'
- script: dotnet tool run dotnet-stryker -tr dotnettest -r "['cleartext', 'html', 'progress']" --solution-path "../../../Company.Product.sln"
workingDirectory: 'tests/domain/Company.Product.Domain.Tests.Unit'
displayName: 'Run Stryker on solution'
- task: PublishMutationReport@0
inputs:
reportPattern: '$(Build.SourcesDirectory)/tests/domain/Company.Product.Domain.Tests.Unit/StrykerOutput/*/reports/mutation-report.html' This is a single job pipeline so isn't multi-stage. |
A new version is released soon which should fix this problem |
Hi, followed the instructions as outlined on the blog and installed the plug in but my build is reporting 0 artifacts
Have a run stryker task
steps:
displayName: 'Stryker - Project'
inputs:
command: custom
custom: 'stryker '
arguments: '-im [''GetHashCode''] -r "[''html'']" -th 90 -tl 80 -tb 50'
workingDirectory: 'project.Test'
This works and logs as expected
Second task
steps:
displayName: 'Publish Mutation Test Report'
inputs:
reportPattern: 'project.Test/**/*.html'
The publish tasks completes without error but no artifact is created and no extra tab displays.
Do i also need to publish this artifact as a final step
Thanks
The text was updated successfully, but these errors were encountered: