We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Given an empty scenario and no step definitions, we're seeing a TestStepStarted and TestStepFinished messages when it runs.
TestStepStarted
TestStepFinished
Expect to see test case messages but not test step messages.
fake-cucumber 16.5.0
Feature: Empty Scenarios Scenario: Blank Scenario
And execute fake-cucumber
See cucumber/compatibility-kit#103.
The text was updated successfully, but these errors were encountered:
In makeTestCase.ts:
makeTestCase.ts
if (pickle.steps.length === 0) { const id = newId() const undefinedStep = new EmptyPickleTestStep( id, undefined, true, [], [], clock, stopwatch, makeErrorMessage ) return new TestCase(newId(), [undefinedStep], pickle.id, clock) }
This explains the current behaviour. It can be removed but some other code will likely need making more defensive as a result.
Sorry, something went wrong.
davidjgoss
Successfully merging a pull request may close this issue.
π What did you see?
Given an empty scenario and no step definitions, we're seeing a
TestStepStarted
andTestStepFinished
messages when it runs.β What did you expect to see?
Expect to see test case messages but not test step messages.
π¦ Which tool/library version are you using?
fake-cucumber 16.5.0
π¬ How could we reproduce it?
And execute fake-cucumber
π Any additional context?
See cucumber/compatibility-kit#103.
The text was updated successfully, but these errors were encountered: