-
-
Notifications
You must be signed in to change notification settings - Fork 655
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation for running Ginkgo outside of go test
#1451
Comments
hey hey @dagan - this has come up a couple of times in the past. long story short: your best bet is to compile the tests (or ship with a precompiled test binary) an orchestrate running them by shelling out and parsing the JSON reporter format. Longer answer: given you’ve looked at some of the code you can see that there are ways to get the DSL to run in-process (the But I think you’ll find that a shelling out to a (potentially precompiled) test suite will largely Just Work™ and be good enough for your usecase. |
Thank you for the response, @onsi. I appreciate the time (and very sincerely appreciate the effort that has gone into Ginkgo and Gomega). ✌️ |
I have a use case for running Ginkgo tests without
go test
, and I am curious if any documentation exists for doing that.I've perused the code base and see that the bulk of test management falls under the
internal
package, which I can certainly understand. Is there something I've missed that exposes the ability to programmatically launch Ginkgo outside of ago test
context?For my specific use case, I'm hoping to utilize Ginkgo's DSL for defining and organizing tests, the ability to filter tests by labels, and of course the reporters, but all integrated within a larger application with use cases separate from Ginkgo's. At this point, I suspect that compiling the tests and launching them independently is the move viable path forward, but I figured I'd at least ask. :-)
The text was updated successfully, but these errors were encountered: