Robert Iannucci
Robert Iannucci
goconvey can't keep track of the test suites across goroutines automatically; this is not permitted by the way the go language/runtime work. Take a close read of the documentation for...
I believe this is already covered with test package profiles? (https://github.com/smartystreets/goconvey/wiki/Profiles)
To clarify, do you mean that the html coverage report is only updated when the test is successful? I've noticed this as well... it's definitely annoying.
I've run into this in tests, and I recommend mocking os.Exit either at the module level (and omitting t.Parallel() in the test function), or somehow passing a mocked osExit to...
(and, of course, you could also potentially split your logic so that you have `func doEverything() int` and `func ExitingFunc() {os.Exit(doEverything())}` and just make tests for `doEverything`)
I'm not sure what the `-depth` argument is meant to be?
Hm... this Should Work™️, but clearly it doesn't... I'll try to take a look at this (and add a test), but I don't have an overabundance of extra time outside...
Ack... I keep losing track of this and haven't had a chance to dig into it. I just took a closer look at this, and I think what's happening is...
I guess when I added the Context support, I was assuming that the tests all pass ^_^. I'm now seeing that the ergonomics when the tests _don't_ pass is pretty...
This _may_ be fixed now (goconvey was completely module-unaware before... it's slightly more aware now...)