You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently found out that a bad merge caused one of our cucumber tests to report as running fine on our build system even though the underlying functionality was broken. It turns out that the test steps that were poorly merged were being reported as undefined but Cucumber was passing anyways. Yikes!
I see Cucumber-js (supports a "Strict" mode](cucumber/cucumber-js#211) where it will return exit code 1 if a step is undefined.
But for the life of me, I can't figure out how to pass "--strict" to chimp. Is there a way? If not, could you point me to where I could add one?
The text was updated successfully, but these errors were encountered:
We recently found out that a bad merge caused one of our cucumber tests to report as running fine on our build system even though the underlying functionality was broken. It turns out that the test steps that were poorly merged were being reported as undefined but Cucumber was passing anyways. Yikes!
I see Cucumber-js (supports a "Strict" mode](cucumber/cucumber-js#211) where it will return exit code 1 if a step is undefined.
But for the life of me, I can't figure out how to pass "--strict" to chimp. Is there a way? If not, could you point me to where I could add one?
The text was updated successfully, but these errors were encountered: