List view
This milestone represents a set of work that results in being able to run the Ginkgo tests in parallel, consistently without spurious failures.
No due date•3/3 issues closed- No due date•8/8 issues closed
With 1.0 out of the way, Version 1.1 is slated to have one big ticket item: - Recursive `watch` should make it possible to trigger tests on watched packages when *dependencies* of these packages change. V1.1 will also have a bunch of smaller features: - Catch erroneously committed focused tests on CI by exiting with a non-0 exit code when focused tests are detected. - A `-failFast` flag which aborts the test run immediately when the first test fails - An `-autoNodes` flag which instructs Ginkgo to run as many parallel nodes as there are processors - `-r` will randomize the suite order (using the `-seed`)
No due date•10/10 issues closedGinkgo 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` and `AfterSuite` - `SynchronizedBeforeSuite` and `SynchronizedAfterSuite` 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 to `ginkgo generate` and `ginkgo 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).
No due date•16/16 issues closed