Better Test Planning:
Tests are clearly defined in the feature file, giving the opportunity to refine and improve before any code is written. Gherkin's syntax also encourages breaking tests into manageable pieces, aiding code organization within the individual test files. Having feature files defined ahead of time would make the process of actually writing the test faster when it is to be done.
Ease of Understanding:
The simple syntax used in Gherkin allows for easy comprehension, making feature files a good place to sanity check any tests that have been written, without having to dig through test code. This would also allow for tests to be defined quickly and with little effort, to be written in full later by whoever has time. Non-technical team members could also define tests using this syntax.
Inspired by Gherkin (https://github.com/cucumber/cucumber/wiki/Gherkin), adding the creation of .feature files to our test creation workflow would provide many benefits:
Better Test Planning: Tests are clearly defined in the feature file, giving the opportunity to refine and improve before any code is written. Gherkin's syntax also encourages breaking tests into manageable pieces, aiding code organization within the individual test files. Having feature files defined ahead of time would make the process of actually writing the test faster when it is to be done.
Ease of Understanding: The simple syntax used in Gherkin allows for easy comprehension, making feature files a good place to sanity check any tests that have been written, without having to dig through test code. This would also allow for tests to be defined quickly and with little effort, to be written in full later by whoever has time. Non-technical team members could also define tests using this syntax.