-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
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
Support Scenario Outlines #62
Comments
Hi Alister, We haven't (still) implemented scenario outlines for a reason: They usually are a "test" smell. We've found out that if you try to be as abstract as possible in your feature definitions, there's barely no situation where scenario outlines are needed. If you're using them, you're probably testing something that should be on a unit test. For example, I've found myself testing the same scenario against different user roles using scenario outlines and that's wrong. Unit tests should guarantee that, and features should always run on the happy path. Also, scenario outlines trend to be less readable than standard feature definitions. In addition, there's a principle we wanted to encourage with spinach: "When you write a feature, you shouldn't be thinking of any semantics more than the language in which you're writing them". Having to think about For example, in your case I would better write two scenarios for that instead of an outline.
So here's why we haven't implemented scenario outlines to the moment. If you can prove us wrong, please feel free to troll us :D What do you think? |
IMHO and experience, scenario outlines are a pain in the ass to debug. Imagine you have something like:
So at first you have them both working, but you change something on your code and now the editor, for some reason you don't know, can't add a post. So you try to debug: add a Even so, when you run |
+1 to @mrcasals |
I think we won't support scenario outlines. I consider them a code smell, since they usually indicate you should be pushing some tests down to lower test layers (functional, unit). Integration tests should be mainly happy path tests. |
Scenario Outlines are not currently supported.
For example
This gives:
even though I created the valid step, it doesn't do the substitution of the value.
The text was updated successfully, but these errors were encountered: