Skip to content

Run cucumber in strict mode#392

Merged
bastelfreak merged 1 commit into
masterfrom
strict
Jun 4, 2025
Merged

Run cucumber in strict mode#392
bastelfreak merged 1 commit into
masterfrom
strict

Conversation

@smortex

@smortex smortex commented Jun 4, 2025

Copy link
Copy Markdown
Member

By default, cucumber do not return an error when some step definitions are missing: it only produce an informational message with code snippet before exiting.

On CI, this is "lost" and when we break a test, it may seem the CI is passing while in fact the test is just broken and not tested anymore.

When running in strict mode, cucumber will exit with an error in such condition.

By default, cucumber do not return an error when some step definitions
are missing: it only produce an informational message with code snippet
before exiting.

On CI, this is "lost" and when we break a test, it may seem the CI is
passing while in fact the test is just broken and not tested anymore.

When running in strict mode, cucumber will exit with an error in such
condition.
@smortex smortex changed the title Run CI in strict mode Run cucumber in strict mode Jun 4, 2025
@bastelfreak bastelfreak merged commit 2b88c97 into master Jun 4, 2025
16 checks passed
@bastelfreak bastelfreak deleted the strict branch June 4, 2025 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants