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.

Sign up for GitHub

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

Jump to bottom

docs(README): Adding full example #4

Merged
merged 1 commit into from
Jun 27, 2024
Merged

docs(README): Adding full example #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,13 @@ errors to be detected. For example:
go test -json 2>&1 | go-junit-report -parser gojson > report.xml
```

Full example, where Go test result is parsed as JSON, the test execution
output is printed as part of go-junit-report and the step fails in case
of test failure.
```bash
go test -json ./... 2>&1 | go-junit-report -set-exit-code -parser gojson -iocopy -out report.xml
```

Go benchmark output is also supported. The following example runs benchmarks for
the package in the current directory and uses the `-out` flag to write the
output to a file called `report.xml`.
Expand Down
Loading