PLCgen self-certification tests: where to put them and announce new versions?

Discussion

So far, we've been developing the PLCgen self-certification tests in #798 (closed). We've been keeping them in a branch named 798-plcgen-s7-300-self-certification-tests. I'd rather not keep the self-certification tests in a separate branch anymore. We may then to forget updating them, as #1102 (closed) shows. It also doesn't seem like a long-term solution to have an never-ending branch.

We integrated the self-certification tests into the PLCgen integration tests as an execution tests folder. However, these files differ slightly, since in the execution folder:

• There is _test_header.txt.
• There are .err files.
• The .csv files of the io* tests don't have a license header, nor instructions on how to adapt the files. This is needed to make the .csv files parsable, since empty lines and comment lines are not supported by the CSV parser.

The question then is: what to do with the self-certification tests.

Some possible options:

• Put the self-certification tests directory in develop, and adapt it there, keeping it separate from the execution tests.
• Derive the self-certification tests from the execution tests, using some script.
• ...?

Besides where to put the self-certification tests, where do we announce changes? It seems wrong to keep reporting them in #798 (closed), since that issue is closed.

Execution

Steps:

• Rename org.eclipse.escet.cif.examples to org.eclipse.escet.cif.models (!1229 (merged))
• Rename integration test plugins from *.tests to *.tests.integration (!1232 (merged))
• Add self-certification tests in org.eclipse.escet.cif.models (!1234 (merged))