Having a similar discussion at work recently, I've written in favour of using Gherkin Features to gather high level requirements (and sometimes a bit of specifi

Having a similar discussion at work recently, I've written in favour of using Gherkin Features to gather high level requirements (and sometimes a bit of specifications), mostly stored in Jira Epics to clarify what's asked. See the post at https://jiby.tech/post/gherkin-features-user-requirements/ https://jiby.tech/post/gherkin-features-user-requirements/ I made this into a series of post about gherkin, where I introduce people to Cucumber tooling and BDD ideals, and show an alternative low-tech for cucumber in test comments. As for actually doing the tracking of feature->test, aside from pure Cucumber tooling, I recommend people have a look at sphinxcontrib-needs: https://sphinxcontrib-needs.readthedocs.io/en/latest/index.html https://sphinxcontrib-needs.readthedocs.io/en/latest/index.h... Define in docs a "requirement" bloc with freeform text (though I put gherkin in it), then define more "specifications", "tests" etc with links to each other, and the tool does the graph! Combined with the very alpha sphinx-collections, it allows jinja templates from arbitrary data: Write gherkin in features/ folder, make the template generate for each file under that folder an entry of sphinxcontrib-needs with the gherkin source being quoted! https://sphinx-collections.readthedocs.io/en/latest/ https://sphinx-collections.readthedocs.io/en/latest/