- Add new section for installing go-junit-report from pre-built
binaries.
- The instructions for installing from source have been updated to use
`go install`, now that `go get` is being deprecated, see #124.
- Move contributing guidelines to separate `CONTRIBUTING.md` file.
Sometimes, the text after "# " shows the name of the test binary
("<package>.test") in addition to the package
e.g.: "# package/name [package/name.test]".
This change ensures that the packages' build outputs are associated
correctly in this case.
The xml annotations currently used allow for marshalling of
the test suites but fail to unmarshal them because of the
lack of an xml annotation on the slice fields for test suites
and test cases.
By adding those annotations, these types can be more widely reused.
Fixes#92
My team spent a bit of time debugging a mistake where we forgot to
redirect output to a file. The command looked valid and exited 0. This
change causes the program to fail if provided with any positional
arguments.
Mainly:
* Moving the averaging/merging of benchmarks from the parser to the formatter package
* Tightening up the regex so it only captures the numeric values (no more of trimming spaces and the ns/op)
* Deleting the writing up in xml file the benchmark memory sections of B/op and Allocs/op
Also added a test case for parseNanoseconds().
- Fix building for go1.10, see travis-ci/travis-ci#9247.
- Add a ".x" suffix to each version so that Travis selects the latest
minor release.
- Remove go1.1, which is not available anymore on Travis.
Whenever we encounter a result line in the test output, we would find
the first test with the matching name and update it. However, in some
cases it's possible for the same test name to appear multiple times in
the output. To prevent us from always updating the oldest test, the
order in which findTests searches for a matching test is reversed so
that it always returns the most recently added test.
Fixes#54.
If a package compiles correctly, but panics before it has a chance to
run any tests it would previously be ignored. Any failing packages
without tests but with some output will now be included in the report
with a dummy test.
Fixes#52
