3 ms·
I just use plain English for that, always a one-sentence summary. Details are for traditional BDD language, which has the advantage of being machine-readable to
by beat 11y ago
I just use plain English for that, always a one-sentence summary. Details are for traditional BDD language, which has the advantage of being machine-readable to generate test stubs.
The purpose of the one sentence summary is not to be complete, but to keep large feature lists readable at a glance.
- everdev 11y agoRight, but is there a common DSL for business logic that's not Gherkin? Something that would be easy enough for stakeholders to read, but also specific enough for developers to write tests against and enter as a ToDo on a Kanban board?
- beat 11y agoNot that I know of. Gherkin is the simplest language I know of with any sort of rigor. Less than that, and you start falling on non-rigorous language that will have gaps of meaning, intent, and completeness. What you came up with was pretty good. Good luck enforcing it with nontechnical stakeholders, though.