[devkit] Improved undefined example(s)#278
Conversation
|
I think it would be better if the existing tests didn't change and one |
|
@davidjgoss I think there's a bug here in fake-cucumber. It looks like when we have multiple steps that are undefined that whilst the snippet generation is working, the status of the subsequent steps is being reported as This doesn't affect the purpose of the tests here per se. But I think it's still wrong as/when I come to implement these once I'm at cckv30+ |
|
closes #276 |
Will make this change in a couple of days. Notwithstanding the fake-cucumber issue as I think this is a bug here |
That was an intentional change in #239, and IIRC it was pointed out by @brasmusson that it works that way already in cucumber-ruby. |
|
I think at that time cucumber-ruby was somewhere between cckv20 and v22 compliant. It's currently cckv24 compliant and I'm working on the v26 compliance. Are we saying that the current implementation is correct, or that we need to make a change. I'm a bit confused sorry |
The current CCK behaviour is correct. |
…ble and one for singular
…ped then undefined again (It should stay skipped)
|
|
||
| Scenario: Steps before undefined steps are executed | ||
| Given an implemented step | ||
| And an implemented step |
There was a problem hiding this comment.
I think we can remove this line. I don't think it meaningfully tests anything related to undefined steps.
| @@ -0,0 +1,18 @@ | |||
| Feature: Examples Tables - With Many Undefined Steps | |||
There was a problem hiding this comment.
I don't think this case is needed at all. Example tables are sugar for repeating the same scenario, which is already covered by the undefined-multiple scenario.
There was a problem hiding this comment.
This was a migration from something left out on the initial implementation
There was a problem hiding this comment.
Not strictly, but it was a bug which was picked up (or will be picked up), so figure in a breaking change (Which this will be), adding this is fine.
| Given an implemented step | ||
| And an implemented step | ||
| And a step that is yet to be defined | ||
| And another step that is also yet to be defined |
There was a problem hiding this comment.
This line looks like we're testing multiple scenarios in on scenario.
We can have two scenarios here, one with one step after an undefined step and one with multiple.
It's also not quite clear what we're testing here.
Either a second step after an undefined step will be skipped (not undefined) or a second undefined step after an undefined step is also undefined (not skipped). It should be clear from reading the scenario what will happen.
There was a problem hiding this comment.
Agreed. Will refactor this
luke-hill
left a comment
There was a problem hiding this comment.
Not sure when I'll get to this. But put some responses and some things I need to fix (Notes to self).
| @@ -0,0 +1,18 @@ | |||
| Feature: Examples Tables - With Many Undefined Steps | |||
There was a problem hiding this comment.
This was a migration from something left out on the initial implementation
There was a problem hiding this comment.
Not strictly, but it was a bug which was picked up (or will be picked up), so figure in a breaking change (Which this will be), adding this is fine.
| Given an implemented step | ||
| And an implemented step | ||
| And a step that is yet to be defined | ||
| And another step that is also yet to be defined |
There was a problem hiding this comment.
Agreed. Will refactor this
|
|
||
| Scenario: Steps before undefined steps are executed | ||
| Given an implemented step | ||
| And an implemented step |
🤔 What's changed?
Update some of the undefined examples to include multi-snippet functionality, so as to prove the cucumber implementor is working well when the snippet generation is > 1 per scenario
⚡️ What's your motivation?
See above
🏷️ What kind of change is this?
♻️ Anything particular you want feedback on?
📋 Checklist:
This text was originally generated from a template, then edited by hand. You can modify the template here.