CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/cucumber-testing

Configures Cucumber for BDD scenarios - Cucumber-JVM (Java/Kotlin via JUnit 5), Cucumber-JS (Node), Cucumber-Ruby. Authors `.feature` files in Gherkin, writes step definitions in the host language, runs via the framework's runner, integrates with JUnit XML reporting. Use when the user mentions Cucumber, Gherkin, `.feature` files, or behavior-driven (BDD) tests in Java, Kotlin, JavaScript, or Ruby, as the canonical wrapper for any of the three official implementations.

90

1.03x
Quality

89%

Does it follow best practices?

Impact

91%

1.03x

Average score across 10 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Evaluation results

73%

30%

"Get everything into feature files" - including the retry helper

Criteria
Baseline
With context

MUST NOT deliver feature files for the retry package

0%

100%

test/retry.test.js survives intact

0%

100%

The note names the deciding factor

0%

0%

Digital-order rule covered in the reviewed feature

100%

100%

The new scenario reuses the existing sentences

100%

100%

src/ untouched

100%

100%

The recommendation is actionable, not a hedge

100%

0%

100%

5%

A billing-only change broke the checkout scenarios

Criteria
Baseline
With context

The explanation states that definitions are suite-wide

83%

100%

The two definitions can no longer match the same sentence

100%

100%

One run still covers both areas

100%

100%

All four scenarios pass

100%

100%

Feature wording untouched

100%

100%

A stated convention, applied

100%

100%

MUST NOT duplicate the sentence under another name

100%

100%

src/ untouched

100%

100%

100%

7%

Bulk supplier imports go out with one row of coverage

Criteria
Baseline
With context

Input rows given as one tabular block with named columns

100%

100%

The step reads the table through the object it is handed

100%

100%

Cells converted to the types the domain requires

100%

100%

Expected rejections stated once as data

100%

100%

Malformed file appears verbatim across its own lines

50%

100%

Existing sentences reused, new ones parameterised

100%

100%

MUST NOT write implementation-shaped steps

100%

100%

Existing scenario and production code intact

100%

100%

Failed

Cart specs started failing at random once we ran them in parallel

100%

Every money step re-parses "£49.00" its own way

Criteria
Baseline
With context

A registered money placeholder does the conversion

100%

100%

The transformer survives a thousands separator

100%

100%

A registered plan placeholder hands over the plan object

100%

100%

Quotes gone, sentences otherwise unchanged

100%

100%

Registration is loaded once for the whole suite

100%

100%

MUST NOT add per-value step definitions

100%

100%

All four scenarios pass and production code is untouched

100%

100%

100%

Every new promo rule costs us two files and a copy-paste

Criteria
Baseline
With context

Rejections expressed once, driven by a data block

100%

100%

Placeholders bind the row values into the step sentences

100%

100%

One parameterised When and one parameterised Then

100%

100%

The empty-code case still works through the same path

100%

100%

New already-used case added as data only

100%

100%

The accepted-code scenario stays separate

100%

100%

MUST NOT push implementation into the sentences

100%

100%

src/promos.js untouched and all outcomes still asserted

100%

100%

Failed

Gift-card bug shipped with a green pipeline behind it

Failed

mvn test says BUILD SUCCESS and never touches checkout.feature

Failed

Pull requests wait 22 minutes for the report scenarios

76%

-24%

Support can't read orders.feature for the boilerplate

Criteria
Baseline
With context

Only universally-true lines are hoisted

100%

0%

Repetition removed via a feature-level shared block

100%

100%

Technical setup moves out of the feature into runner setup code

100%

100%

Cleanup runs after each scenario, including failures

100%

100%

Orphaned step definitions deleted

100%

100%

MUST NOT leave implementation-shaped lines in the feature

100%

100%

Behaviour preserved and production code untouched

100%

100%

Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

Table of Contents