« Changelog History


ginkgo v1.2.0-beta Release Notes

  • Ginkgo now requires Go 1.4+

    👌 Improvements:

    • 0️⃣ Call reporters in reverse order when announcing spec completion -- allows custom reporters to emit output before the default reporter does.

    • 👌 Improved focus behavior. Now, this:

      FDescribe("Some describe", func() {
    It("A", func() {})

    FIt("B", func() {})
})

    will run B but not A. This tends to be a common usage pattern when in the thick of writing and debugging tests.

    • ✅ When SIGINT is received, Ginkgo will emit the contents of the GinkgoWriter before running the AfterSuite. Useful for debugging stuck tests.
    • ✅ When --progress is set, Ginkgo will write test progress (in particular, Ginkgo will say when it is about to run a BeforeEach, AfterEach, It, etc...) to the GinkgoWriter. This is useful for debugging stuck tests and tests that generate many logs.
    • 👌 Improved output when an error occurs in a setup or teardown block.
    • When --dryRun is set, Ginkgo will walk the spec tree and emit to its reporter without actually running anything. Best paired with -v to understand which specs will run in which order.
    • ➕ Add By to help document long Its. By simply writes to the GinkgoWriter.
    • ➕ Add support for precompiled tests:
      • ginkgo build <path-to-package> will now compile the package, producing a file named package.test
      • The compiled package.test file can be run directly. This runs the tests in series.
      • To run precompiled tests in parallel, you can run: ginkgo -p package.test
    • 👌 Support bootstrapping and generateing Agouti specs.
    • 📦 ginkgo generate and ginkgo bootstrap now honor the package name already defined in a given directory
    • ✅ The ginkgo CLI ignores SIGQUIT. Prevents its stack dump from interlacing with the underlying test suite's stack dump.
    • ⬆️ The ginkgo CLI now compiles tests into a temporary directory instead of the package directory. This necessitates upgrading to Go v1.4+.
    • 🐧 ginkgo -notify now works on Linux

    🐛 Bug Fixes:

    • 📦 If --skipPackages is used and all packages are skipped, Ginkgo should exit 0.
    • 🛠 Fix tempfile leak when running in parallel
    • 🛠 Fix incorrect failure message when a panic occurs during a parallel test run
    • 🛠 Fixed an issue where a pending test within a focused context (or a focused test within a pending context) would skip all other tests.
    • Be more consistent about handling SIGTERM as well as SIGINT
    • ✅ When interrupted while concurrently compiling test suites in the background, Ginkgo now cleans up the compiled artifacts.
    • 🛠 Fixed a long standing bug where ginkgo -p would hang if a process spawned by one of the Ginkgo parallel nodes does not exit. (Hooray!)