feat: xUnit output project #372
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mefellows
approved these changes
Feb 19, 2022
adamrodger
force-pushed
the
feat/xunit-output
branch
from
2b563bc
to
4beacd0
Compare
adamrodger
force-pushed
the
feat/xunit-output
branch
from
4beacd0
to
bd90e87
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's so simple, in fact it's trivial, but it's something you end up having to copy and paste over and over so it's probably better as a tiny NuGet package.
It can't be released officially until 4.0.0 is fully released otherwise it'll depend on a prerelease version of
PactNet.Abstractions