Skip to content

Commit 825b411

Browse files
committed
Blog post about release 4.7.0.
1 parent 978cd10 commit 825b411

1 file changed

Lines changed: 46 additions & 0 deletions

File tree

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
---
2+
title: "OpenFastTrace 4.7.0 released: Gherkin Importer"
3+
date: 2026-08-01
4+
draft: false
5+
author: "sebastian"
6+
---
7+
8+
OpenFastTrace 4.7.0, codenamed "Gherkin Importer", is now available. This release introduces direct support for Gherkin `.feature` files as specification sources and enables requirement coverage within Markdown and reStructuredText (RST) comments.
9+
10+
## Gherkin Specification Import
11+
12+
The most significant addition in this release is the ability to import specification items directly from Gherkin `.feature` files. This allows teams using Behavior-Driven Development (BDD) to integrate their executable specifications directly into their traceability matrix.
13+
14+
OpenFastTrace now recognizes `Scenario` and `Scenario Outline` blocks as specification items when they are annotated with an OFT ID tag. You can also specify "coverage" and "needs" metadata using comments immediately following the tags.
15+
16+
Example of an annotated Gherkin scenario:
17+
18+
```gherkin
19+
@id:scn~user-login~1
20+
# Covers: req~authentication~1
21+
# Needs: dsn, itest
22+
Scenario: Successful login with valid credentials
23+
Given the login page is open
24+
When the user enters valid credentials
25+
Then the user should be redirected to the dashboard
26+
```
27+
28+
## Coverage in Documentation Comments
29+
30+
This release expands the Tag Importer to support native comments in Markdown and reStructuredText (RST) files. This allows documentation to cover specification items without the coverage tags being visible in the rendered output.
31+
32+
In Markdown, you can now use standard HTML comments for coverage:
33+
34+
```markdown
35+
<!-- [impl -> req~user-manual-updated~1] -->
36+
```
37+
38+
Similarly, in reStructuredText, native comments are supported:
39+
40+
```rst
41+
.. [impl -> req~user-manual-updated~1]
42+
```
43+
44+
This feature is useful for maintaining traceability in user manuals, architectural decision records, and other documentation where explicit coverage tags might disrupt the flow for the reader.
45+
46+
For a detailed list of changes, please see the [official release notes](https://github.com/itsallcode/openfasttrace/releases/tag/4.7.0).

0 commit comments

Comments
 (0)