Comments (5)
Unfortunately go-junit-report doesn't yet support any kind of non-standard test outputs, but it would be great if it did. Are you're willing to add support for testify? I'd be more than happy to discuss details and review code.
from go-junit-report.
Faced the same issue. Will think about the solution.
from go-junit-report.
hello @jstemmer - I'm thinking about implementing this feature just for fun so I have question to you: do you think that we can treat test suite just like Package struct used in your code ? As I can see packages are generating output in separate testsuite blocks (like in 06-report.xml in tests)
from go-junit-report.
Do you mean that you want to create a separate package for every testsuite in the testify output? That could probably work. I haven't used testify myself however, so I'm not sure how easy it is to differentiate test suites from individual tests.
It's probably a good idea to first collect a few different testify outputs and think about how that would be represented in the resulting XML.
from go-junit-report.
This appears to be fixed in v2, feel free to reopen if it's not the case.
from go-junit-report.
Related Issues (20)
- Trimming module name from classname HOT 4
- unable to install go-unit-report HOT 3
- after I use "go test xxx 2>&1 | go-junit-report > result.xml", then the console doesn't print any more information HOT 4
- go-junit-report is failing with command not found...
- `-version` info is "not as useful" as it may should've been
- have an option to exclude succeeded tests
- zsh: command not found: go-junit-report HOT 3
- [no test files] Not handled well by set-exit-code
- New release HOT 2
- False error report in case of json parsing HOT 1
- Include arm64 builds in release assets
- gotest output from 1.20+ is not properly parsed
- `flag provided but not defined: -in`
- go-junit-report reports success after failing to compile code HOT 1
- benchmark tests marked as error when no unit test found HOT 1
- `system-out` is never placed under the correct `testcase` HOT 2
- Consider adding an option to prevent parsing lines starting with `#` as build output
- Better support of multiple test runs (`-count`)
- Linux arm64 binary missing HOT 1
- Capture test failures
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from go-junit-report.