Skip to content
SPECIFICTION
Get listed

Cucumber Open vs LightBDD

Cucumber Open

cucumber.io

LightBDD

github.com

Side by side

FigureCucumber OpenLightBDD
Price fromFreeFree
Free planYesYes
Free trial——
Open source——
WindowsYesYes
macOSYesYes
LinuxYesYes
AndroidYes—
APIYes—
Plans published11
Spec score · BDD Testing Tools8.2 (#6)7.5 (#17)
PurposeCucumber runs automated acceptance tests written in plain language that can be read by anyone on a team.LightBDD is a behavior driven development framework for writing readable tests and tracking their execution.

Plans

Cucumber Open

  • Cucumber OpenFree

Cucumber Open pricing →

LightBDD

  • Free and open sourceFree

LightBDD pricing →

In their own words

Cucumber Open

Cucumber Open runs automated acceptance tests from specifications written in plain language, helping teams check whether software behaves as described. It supports Behaviour-Driven Development by executing Gherkin specifications saved in `.feature` text files, typically alongside software in source control. Step definitions link the specification's steps to code that carries them out. Official implementations include JavaScript, Java, Ruby, Android Java, Kotlin, Scala, and C++, with semi-official and unofficial implementations also listed. Gherkin has variations for spoken languages, so teams can use keywords in their own language. Reporting options include built-in HTML, JSON, JUnit, and progress formatters, as well as custom formatters. Cucumber can run in continuous integration environments; its documentation describes JUnit output and a Jenkins reporting plugin. The project is free and open source, with local execution, parallel execution, browser testing, and API access. Published Cucumber Reports are public without authentication and deleted after 24 hours; the report service says data is stored in US data centers and encrypted at rest.

Visit cucumber.io

LightBDD

LightBDD is a free, open-source behavior-driven development framework for writing readable tests and tracking execution locally. Scenarios support parameterized steps, inline and tabular parameters, and shared context. The framework records step progress and execution time and supports asynchronous scenarios and steps. It generates feature reports in HTML, XML, or plain text. Listed integrations include NUnit, xUnit 2 and 3, Microsoft Test Framework, Fixie, and TUnit, while dependency-injection containers are supported. A Visual Studio extension supplies project and feature-class templates plus snippets for scenarios and composite steps. The Quick Start organizes acceptance tests as partial feature classes, separating scenario definitions from step implementations. Packages are distributed through NuGet. Listed runtime support includes .NET 5+, .NET Framework, .NET Standard, .NET Core, and UWP. LightBDD runs on Linux, macOS, and Windows under the BSD 2-Clause License. The project wiki and NuGet debug symbols provide support and diagnostics resources. A community project can synchronize LightBDD scenarios with Azure DevOps test cases.

Visit github.com