Releases: GoTestTools/gotestfmt
v2.5.0
What's Changed
- A hash character at the beginning of Output line causes test to be marked as failed by @JackuB in #52
- Add support for overriding template dir by @obfu5c8 in #50
New Contributors
Full Changelog: v2.4.1...v2.5.0
v2.4.1
v2.4.0
This is a technical release as we are moving to the GoTestTools organization.
Full Changelog: v2.3.2...v2.4.0
v2.3.2
v2.3.1: Bugfixes for go-acc
This release fixes #39, where a gotestfmt crashes when a syntax error is reported after a successful package. Furthermore gotestfmt now ignores the extra output inserted by go-acc.
Full Changelog: v2.3.0...v2.3.1
v2.3.0: Non-zero exit status on test failure
This release changes the exit code of gotestfmt to a non-zero status if one or more tests fail. This behavior is consistent with the exit status of go test. We have added this to make sure CI doesn't pass on failing tests if users forget to add set -euo pipefail. This behavior can be disabled by passing the -nofail option in the command line.
Thank you to @gabesullice for reporting this issue.
v2.2.0: Output Formatters
v2.1.0
As a first community contribution, @MartinPetkov has sent in a patch that adds a flag to print the status text (PASS, FAIL, SKIP) in written words next to the icons. We also have a list of bugfixes.
The following pull requests have been merged:
v2.0.1
v2.0.0: JSON test output
This release contains a backwards-incompatible change and only supports output generated with go test -json. Please switch your test configuration to output in the JSON format.
We are sorry we had to break backwards compatibility, but this was the only way to fix bug #8, where tests were incorrectly shown in the wrong package.
Docker images
docker pull ghcr.io/haveyoudebuggedit/gotestfmt:v2.0.0docker pull ghcr.io/haveyoudebuggedit/gotestfmt:v2
