The `newlineReporter` intends to print a new line after the test to prevent the something print to the stdout and mess up the test result while cause the tool like `go-junit-report` fail to parse the result. But this is no longer needed based on following evidence. - The issue that was first introduced in `go-junit-report` has already fixed in the version referenced in `go.mod`. - The `newlineReporter` report doesn't fix anything for `Ginkgo` v1 or V2 or `go test`, it just prints a new line before the test summarization. Signed-off-by: Dave Chen <dave.chen@arm.com> Kubernetes-commit: 9953dde65dfaede9f1d481296053adc301ad9773 |
||
|---|---|---|
| .. | ||
| parse | ||
| strategy | ||
| doc.go | ||
| element.go | ||
| empty_element.go | ||
| error.go | ||
| list_element.go | ||
| map_element.go | ||
| primitive_element.go | ||
| type_element.go | ||
| visitor.go | ||