v0.4.0

Hello everyone! We are releasing a new version of codeplain - 0.4.0!

Upgrade with uv tool upgrade codeplain.

Breaking

• Test scenarios move out of the .plain file into a test plain file of their own, one file per functionality, under a tests folder. Use the add-test-scenarios skill of plain-forge to write them.
• Every functionality needs a test plain file when a conformance tests script is set. The render stops and names the file to write.
• --render-range and --render-from take the ID of a functionality, the one you write in its heading, in place of its number.
• A build folder made by an older version cannot be continued, because it recorded functionalities by number. Remove it and render again.

New

• --tests-folder names the folder that holds the test plain files. Repeat it for more than one. It defaults to tests beside the .plain file, so a project that follows the convention needs no setting. The tests-folder key of config.yaml does the same.
• A functionality whose test plain file holds no scenario is rendered without conformance tests. The tests of the functionalities before it still run.
• The renderer warns when a written scenario got no test, when a test belongs to no scenario, and when one scenario got more than one test.
• Every message names a functionality as its module and ID, in the progress view, the log and the render report.

Internal

• plain-parser 0.2.0.

Full Changelog: v0.3.13...v0.4.0