I'd like to move my tests into the packages they're testing so that I can stop exporting internal functions. Doing that is relatively straight-forward, but maintaining the tie-in to my project-wide "suite test"/ginkgo setup such that "go test" works isn't obvious. Can someone shed some light on how I can have these tests scattered throughout my project, but still be able to run the entire suite?
Up to this point I've been putting all of my tests into a "tests" directory and testing packages externally. That being said, I'd like to be able to access package internals to simplify my tests; I don't want to have to examine state externally, since some of these checks would be somewhat exhaustive. I'm currently exporting functions that I'd rather not, just for the sake of testing.
I'd like to move my tests into the packages they're testing so that I can stop exporting internal functions. Doing that is relatively straight-forward, but maintaining the tie-in to my project-wide "suite test"/ginkgo setup such that "go test" works isn't obvious. Can someone shed some light on how I can have these tests scattered throughout my project, but still be able to run the entire suite?
--
https://github.com/onsi/ginkgo
https://github.com/onsi/gomega
---
You received this message because you are subscribed to the Google Groups "Ginkgo And Gomega" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ginkgo-and-gom...@googlegroups.com.
To post to this group, send email to ginkgo-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/ginkgo-and-gomega.
To view this discussion on the web visit https://groups.google.com/d/msgid/ginkgo-and-gomega/467a761e-da8c-46db-99ac-c2fc541b6e20%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.