Ginkgo is close to the big 1.0
I'm taking this opportunity to perform a sweeping refactor. There will be a few minor backward incompatibilities (mainly around custom reporters and the gomock helper) that should be relatively straightforward to fix. I'll update the docs, the readme, and this milestone as these background-incompatible changes come up.
If you want to follow along, you can take a look at the refactor branch.
Things that I'm hoping will land in 1.0:
- Major refactor & cleanup & many new integration tests - will make future features that much easier to implement.
BeforeSuite
andAfterSuite
SynchronizedBeforeSuite
andSynchronizedAfterSuite
for setting up singleton resources across parallel nodes.- Improved succinct mode (running Ginkgo against multiple packages will automatically enter succinct mode, running just one package will not)
- It'll be possible to pass custom flags/args along to your test suite via
ginkgo <flags> <packages> -- <custom args/flags>
- A
--skipPackage
flag that takes a regex and completely skips packages that match said regex - A
--trace
flag that causes failures to print out entire stack traces, not just the line of code where the failure was emitted. - Putting cleanup in Ginkgo was a bad idea. It's moving to github.com/onsi/gocleanup or something.
- A
--nodot
flag toginkgo generate
andginkgo bootstrap
that will avoid the controversial.
imports by explicitly importing all exported Ginkgo and Gomega functions/types/variables into the top-level namespace. This will allow you to rename individual things if they conflict with your own namespace.
Once 1.0 lands Ginkgo will adopt semantic versioning and there should not be any annoying backward-incompatible breaking changes (hopefully).
List view
0 issues of 0 selected
There are no open issues in this milestone
Add issues to milestones to help organize your work for a particular release or project. Find and add issues with no milestones in this repo.