Quality Requirements as Gherkin feature files

[aheusingfeld]

I'm currently using Gherkin feature files (https://docs.cucumber.io/gherkin/reference/) to enable my teams to contribute Quality Scenarios which might otherwise be missed. These are most often (implicit) assumptions they make while working on the code. Via scenarios in Gherkin (http://docs.behat.org/en/v2.5/guides/1.gherkin.html) these are now made explicit and brought to the attention of the other people in the project e.g. the product owner. The product owner can then evaluate whether the assumption is correct or not.

I'm wondering whether rewriting this repository in this way might actually make it more accessible to others - and I wouldn't have to explain the approach over and over again. ;)

Let me know your thoughts

[gernotstarke]

in principle, the (old-fashioned) quality-scenarios as initially described by the SEI seem to be quite similar in structure to the Gherkin scenarios - the latter usually being executable.

The idea of re-writing our scenarios in Gherkin sounds very interesting to me - alas I have never before seen quality-requirements written down in BDD fashion...

Could you/your team provide some examples, and we decide a potential migration/transition based upon those samples? (I personally cannot commit time until mid-october 2018)