Skip to content
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

Command option to disable trx output #29

Closed
Tasteful opened this issue Aug 27, 2024 · 1 comment · Fixed by #31
Closed

Command option to disable trx output #29

Tasteful opened this issue Aug 27, 2024 · 1 comment · Fixed by #31

Comments

@Tasteful
Copy link
Contributor

Tasteful commented Aug 27, 2024

I trying to use the dotnet-retest in my DevOps Server pipeline, I write the test into trx files directly that I pushing into DevOps Server for the build and that is working and test result is presented in the test-tab.

But, the list of all executed test is bloating the console log for the build and I should like to disable the trx summary output.

Is there a change that we can add an extra switch in this if-statement to be able to turn it off? I can do a PR if you think this is a good idea.

Back this issue
Back this issue

kzu added a commit that referenced this issue Sep 2, 2024
Since this uses the dotnet-trx command, the easy way is to disable reporting entirely (which will also disable GH reporting).

Fixes #29
@kzu
Copy link
Member

kzu commented Sep 2, 2024

This is great feedback. I have a fix in place, a new --no-summary switch. Shipping it soon. Thanks!

Should be out as v0.6.3

kzu added a commit that referenced this issue Sep 2, 2024
Since this uses the dotnet-trx command, the easy way is to disable reporting entirely (which will also disable GH reporting).

Fixes #29
@kzu kzu closed this as completed in #31 Sep 2, 2024
@devlooped devlooped locked and limited conversation to collaborators Feb 19, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants