Joeri Exelmans
14719055bb
Action language components are now completely independent from anything statechart-related.
|
%!s(int64=5) %!d(string=hai) anos | |
|---|---|---|
| .. | ||
| legacy_test_files | %!s(int64=5) %!d(string=hai) anos | |
| lib | %!s(int64=5) %!d(string=hai) anos | |
| test_files | %!s(int64=5) %!d(string=hai) anos | |
| wontfix | %!s(int64=5) %!d(string=hai) anos | |
| README.md | %!s(int64=5) %!d(string=hai) anos | |
| legacy_render.py | %!s(int64=5) %!d(string=hai) anos | |
| legacy_test.py | %!s(int64=5) %!d(string=hai) anos | |
| render.py | %!s(int64=5) %!d(string=hai) anos | |
| test.py | %!s(int64=5) %!d(string=hai) anos | |
README.md
test.py
The Python program test.py replaces the old run_tests.py. It takes test input files (in SCCD XML format) as parameter. It compiles tests and runs them.
For example, to run the "semantics" tests:
python3 test.py test_files/semantics
This will create a 'build' directory with compiled statechart models. It is always safe to remove this directory, it merely serves as a 'cache' for build artifacts.
render.py
The Python program render.py renders the test file state machines as SVG images. Rendered SVG files are already checked in to this repository. If you wish to re-render them, you need the NPM (NodeJS) package state-machine-cat. Install NodeJS and NPM, and then install the NPM package 'state-machine-cat':
npm i -g state-machine-cat
Now, e.g. render the "semantics" tests:
python3 render.py test_files/semantics
By default, the SVG files are stored next to the test XML files.