Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Support Scenario Outlines #62
Scenario Outlines are not currently supported.
even though I created the valid step, it doesn't do the substitution of the value.
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