Three related changes to the documentation.
-
Update the Development Tools section (docs/source/development.rst) to include an explanation of the @wip tag, and how the test data flows from cel-spec to the features directory tree with tags injected by the gherkinize.py tool.
-
Add a link to this to the README.rst to provide a clear path to show how @wip tags are injected into the tests.
-
Add a page with the complete list of features, showing ✅ and ❌ for the features supported and the features marked @wip. (It's not clear precisely how to do this. It might be an useful secondary output from the gherkinize.py tool.)
Three related changes to the documentation.
Update the Development Tools section (
docs/source/development.rst) to include an explanation of the@wiptag, and how the test data flows from cel-spec to thefeaturesdirectory tree with tags injected by thegherkinize.pytool.Add a link to this to the
README.rstto provide a clear path to show how@wiptags are injected into the tests.Add a page with the complete list of features, showing ✅ and ❌ for the features supported and the features marked
@wip. (It's not clear precisely how to do this. It might be an useful secondary output from thegherkinize.pytool.)