Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Ginkgo

onsi.github.io

  • Free plan
  • Windows
  • macOS
  • Linux
7.9 Club score Visit onsi.github.io

What Ginkgo is

Ginkgo is a free, MIT-licensed testing framework for Go that helps developers write expressive specifications. Its BDD-style DSL structures suites with nested Describe, Context, and When containers, along with setup, cleanup, and spec nodes. It can be used for unit, integration, and performance testing. Independent specs can run in parallel and in reproducibly randomized order. The bundled ginkgo command can generate, run, filter, and profile suites, and watch for changes to rerun specs. Reporting can produce machine-readable output in multiple formats and can be customized. Ginkgo builds on Go's testing foundation and is designed to pair with the Gomega matcher library. Its GinkgoT() and GinkgoTB() interfaces also support using many Go testing libraries, including Testify and Gomock. Documentation lists completions for Sublime Text and VS Code, plus a VS Code extension for running specs. Ginkgo V2 is the current supported major version; V1 is no longer supported. Compatibility is guaranteed for Go versions currently supported under Go's release policy, N and N−1.

Who it suits

Ginkgo suits Go developers who prefer a behavior-driven, nested specification style for tests. It can also work for teams that need parallel execution or machine-readable reporting.

Good to know, and what to watch

  • Supports unit, integration, and performance specs.
  • Can randomize and parallelize independent specs.
  • CLI generates, filters, and profiles suites.
  • Reporting supports multiple machine-readable formats.
  • Works with many Go testing libraries.
  • Ginkgo V1 is no longer supported.
  • Bug fixes are not back-ported.

Ginkgo

Free

Free plan

Getting started

  1. Open https://onsi.github.io/ginkgo/
  2. Install Ginkgo in a Go project
  3. Use the ginkgo command to generate a suite
  4. Write specs with Describe, Context, When, setup, cleanup, and spec nodes
  5. Run, filter, profile, randomize, or parallelize suites with the CLI
  6. Add Gomega or compatible Go testing libraries as needed

Limits to check

The supported major version is V2; Ginkgo V1 is no longer supported. Compatibility is guaranteed for Go versions currently supported under the N and N−1 release policy.

The Club's review

Ginkgo is a Go testing framework for developers who prefer a specification-style approach to test suites. It is a strong fit for Go projects that need structured unit, integration, or performance specs, but it is not a general-purpose testing platform for other languages.

Overview

Ginkgo builds on Go’s testing foundation and organizes tests with nested Describe, Context, and When containers, plus setup, cleanup, and spec nodes. That structure gives related cases a clear home, particularly for developers familiar with Quick, RSpec, Jasmine, or Busted. Teams that prefer simpler, flatter Go tests may find the additional DSL structure unnecessary.

The framework is designed to use Gomega for matchers, while GinkgoT() and GinkgoTB() allow many other Go testing libraries, including Testify and Gomock. This makes it possible to adopt Ginkgo’s suite organization without giving up those libraries. Ginkgo supports unit, integration, and performance specs, so the same framework can serve several testing needs within a Go project.

Key features

Execution and CLI

Ginkgo can reproducibly randomize spec order and run independent specs in parallel. Repeatable randomization helps reveal tests that depend on execution order without making a failure difficult to reproduce; parallel execution can help teams run independent work concurrently. The bundled ginkgo command generates and runs suites, filters and profiles them, and watches for changes to rerun specs. That breadth makes it useful for developers who want suite management close to their Go workflow.

Reporting and development workflow

Reporting supports machine-readable output in multiple formats as well as custom reporting infrastructure, which gives teams room to adapt results to their own workflows. The CLI can produce GitHub Actions-friendly output, and the documentation recommends flags for CI runs. Documentation also lists completions for Sublime Text and VS Code, along with a VS Code extension for running specs. These integrations make the framework more practical in editor and CI workflows, though they remain centered on Go development.

Ginkgo is MIT-licensed and free. It follows semantic versioning in the 2.m.p line: minor releases are intended to add functionality and patch releases to fix bugs, with fixes not back-ported. Compatibility is guaranteed with the currently supported Go versions N and N−1 under Go’s release policy. Ginkgo V1 is no longer supported, so new adopters should use V2.

Pricing

Ginkgo is free, with a Ginkgo plan at free. The plan provides the Go testing framework, and the current supported major version is V2. There are no paid tiers or seat-based limits in this plan, making it straightforward for individual developers and teams to use without a subscription decision. The trade-off is scope: this is a Go framework, not a paid cross-language testing suite.

Platforms

Ginkgo supports Linux, macOS, and Windows. Its execution mode is local, with parallel execution supported. It also supports Gherkin and API access, extending its use beyond basic local unit-test runs while remaining part of a Go-focused testing workflow.

Who it's for

Ginkgo suits Go developers who want nested, expressive test specifications, repeatable randomized runs, parallel execution, or command-line support for managing suites. Teams already using Gomega, Testify, or Gomock can integrate those libraries into the workflow. It is less appropriate for teams seeking a multi-language authoring environment or those who do not want a specification-oriented DSL.

Questions, bug reports, and feature requests are directed to GitHub Issues or the project’s Slack channel. That gives users community routes for help, rather than a commercial support tier.

Pros and cons

  • Pros: The nested DSL groups related specs with setup and cleanup, which can make larger test suites easier to organize.
  • Pros: Reproducible randomization and parallel execution support order checks and concurrent runs.
  • Pros: The CLI combines suite generation, filtering, profiling, and watch mode, while reporting covers machine-readable output and customization.
  • Pros: Free, MIT-licensed use and compatibility with several Go testing libraries lower the cost of adopting it within an existing Go project.
  • Cons: Its DSL, integrations, and compatibility policy are tied to Go, so teams testing other languages need another tool.
  • Cons: V1 is unsupported and fixes are not back-ported, so projects still on V1 must plan around the supported V2 line.

Alternatives

For a different approach to BDD testing, browse BDD Testing Tools. Choose CukeTest instead if visual feature editing and JavaScript or Python matter more; its free Lite plan includes 500 automation API calls, while some built-in automation libraries have usage limits. Serenity BDD is a free open-source library to consider for projects spanning platforms including mobile and web; its JUnit 4 support is deprecated and planned for removal in Serenity 6.0.0.

Cucumber Open is another free open-source option, with free Cucumber Reports. Choose FitNesse if an open-source project without stated commercial plans or limits better matches your needs. Karate may suit teams looking for a free MIT-licensed framework that covers REST, GraphQL, and SOAP API testing, browser and desktop UI automation, and Gatling performance testing.

Reqnroll offers a free Community plan with framework usage, Visual Studio and Rider integration, community plugins, and community support; choose it if that ecosystem is a better fit. BddDotNet is a free, MIT-licensed alternative. Concordion is a free Java library under the Apache License 2.0, a fit to consider for Java projects.

Verdict

Choose Ginkgo for a Go project that benefits from structured specifications, repeatable randomized execution, parallel runs, and a capable CLI at no cost. Its integration with existing Go testing libraries keeps adoption flexible. Look elsewhere if you need one testing environment for multiple languages, or if your project still depends on unsupported Ginkgo V1.

The verdict

Ginkgo offers a structured testing workflow with CLI and reporting options for Go projects. New adopters should target V2, the supported major version.

Questions people ask

Does Ginkgo cost anything?

No. Ginkgo is free, and its repository states that it is MIT-licensed.

Which operating systems are supported?

The listed platforms are Linux, macOS, and Windows.

What kinds of tests can it run?

Ginkgo supports unit, integration, and performance specifications.

Can specs run in parallel?

Yes. Independent specs can run in parallel, with reproducibly randomized execution order.

What is the current supported version?

V2 is the current supported major version. V1 is no longer supported.

Which matchers and libraries work with it?

Ginkgo is designed to pair with Gomega and exposes GinkgoT() and GinkgoTB() for libraries including Testify and Gomock.

What the maker publishes

BDD-style DSL
Its DSL supports nested Describe, Context, and When containers, setup and cleanup nodes, and spec nodes. source
CI
The CLI supports GitHub Actions friendly output, and the docs recommend a set of flags for continuous integration runs. source
CLI
The bundled ginkgo command can generate, run, filter, and profile suites, and watch for changes to rerun specs. source
CLI
The Ginkgo CLI can bootstrap and generate test files, run suites, watch for changes, and build test binaries. source
Compatibility
The current Ginkgo version is guaranteed to be compatible with the currently supported Go versions N and N−1 under Go's release policy. source
Execution
Ginkgo supports reproducibly randomizing spec order and running specs in parallel. source
Founded
2013 source
IDE support
The documentation lists completions for Sublime Text and VS Code, plus a VS Code extension for running specs. source
Integration
Ginkgo is built on Go's testing foundation and is complemented by the Gomega matcher library. source
Integrations
Ginkgo exposes GinkgoT() and GinkgoTB() so many Go testing libraries, including Testify and Gomock, can be used with it. source
Intended users
The project describes its DSL as familiar to users of Quick, RSpec, Jasmine, and Busted. source
Intended users
The documentation assumes users are familiar with Go and the Go toolchain. source
License
The repository states that Ginkgo is MIT-Licensed. source
Matchers
Ginkgo is designed to be paired with Gomega, which provides its matcher library. source
Purpose
Ginkgo is a mature testing framework for Go designed to help developers write expressive specs. source
Purpose
Ginkgo is a testing framework for Go for writing expressive tests, including unit, integration, acceptance, and performance tests. source
Reporting
Its reporting infrastructure can generate machine-readable output in multiple formats and supports custom reporting infrastructure. source
Reporting
Ginkgo provides CLI support for generating and aggregating machine-readable reports, plus extensible reporting for custom formats. source
Support
The project directs users with questions, bug reports, and feature requests to GitHub Issues or its Slack channel. source
Test execution
Ginkgo supports randomized and parallel execution of independent specs. source
Testing scope
Ginkgo can be used for unit, integration, and performance specs. source
Version limitation
Ginkgo V1 is no longer supported; the documentation identifies V2 as the current supported major version. source
Version policy
Ginkgo follows semantic versioning in the 2.m.p line, with minor releases intended for new functionality and patch releases for bug fixes; fixes are not back-ported. source

Checked against the maker's pages on 30 Sept 2026.