I want to exhaustively test a set of pages with behat.
For example, this Scenario Outline:
Scenario Outline:
Given I am at <path>
When I click some button
Then I should see <hidden-stuff>
| path | hidden-stuff |
| path1 | element1 |
| path1 | element2 |
| path1 | element3 |
| path2 | element1 |
| path2 | element2 |
| path2 | element3 |
| path3 | element1 |
| path3 | element2 |
| path3 | element3 |
...
In my specific case, I have over 10 examples and 50 paths, so you can see how this becomes extremely unwieldy. I'm trying to avoid an unmaintainable feature with 500 rows, which needs to be edited every time I add a new path or more elements.
Can I feed the results of a mysql query into the "" parameter?
Or supply "path" on the command line or via environment?
Is there a better way to approach this problem?
edit: I did find this post, which basically wrests all the logic out of the .feature file (Gherkin) and into the FeatureContext (PHP). But that doesn't seem like a stakeholder-friendly way to do behat. Is that really the best / only approach?