Skip to main content

0.8.4 — Your tags, and what they mean

Released 2026-08-05.

Scenario tags told a reader which kind of test a scenario was. This release makes sure they can also find out what your organisation means by them.

What's new​

Custom tags of your own. Add tags the shipped catalogue doesn't cover — a regulatory category, a subsystem marker, a house convention. A custom tag appears in the Tag Glossary alongside the system tags of its category and is sent to the story generator on the same terms. Names may now contain a colon as a namespace separator (risk:integration-failure), and run to 64 characters. A custom tag can't take a system tag's name — override the system tag instead, which remains the only way to change what a shipped tag means.

Accepting a proposal now adopts it. When the generator invents a tag, accepting it from the review queue promotes it into your vocabulary and removes it from the queue, so it's available to the next generation run. You can revise the name, category, definition or usage before accepting.

Tag definitions travel with your release. A handover now carries the vocabulary the release actually uses — each tag's category, definition and usage note — together with the application's test strategy. Available from the API and in the exported release PDF, under Appendix B — Scenario tags. A downstream reader receiving @test:holdback on a scenario can now look up what you meant by it.

Bug fixes​

  • A custom tag whose name matched no system tag was stored, but never appeared in the Tag Glossary and was never sent to the generator. It now does both. If you created custom tags previously and wondered where they went, they are there.
  • Accepting an AI-proposed tag saved your edits but left the tag in the review queue permanently, so it never joined the vocabulary and the generator kept re-proposing the same names. Accepted tags now leave the queue.

Behind the scenes​

  • Tags are extracted from Gherkin structurally rather than by scanning for @, so email addresses and quoted tag names in step text can never be mistaken for tags.
  • The vocabulary is now assembled in one place shared by the glossary page, the generation prompt, the API and the PDF, so the four can no longer disagree.

Upgrade notes​

The scenario_tags.tag_name column widens from 50 to 64 characters. Existing tags are unaffected. No action is required.