Tests

Automatic JUnit test can tests are executed in each continuous integration build in Bamboo. The can also be run locally in your KIELER development environment. They are also execute in each continuous integration build in Bamboo.

All tests are located in the test folder of the semantics repository. Most the perform their test on models loaded from the models repository.
Executing these test requires to clone a local checkout of the repository locally and . It is also necessary to set the following environment variable for testwhen executing the tests:

models_repository=path/to/models/repository

Models Repository

...

The models repository uses property files to detect and configure models used in tests.

The properties associated with a model file are derived from a hierarchy of property files. All files named directory.properties assign properties to the directory the are placed and all subdirectories. Files named modelA.properties assign properties to all files in the same diretory with the same filename, i.e. modelA.sct or modelA.broken.sct.

There are some predefined properties which generally control model detection and categorization but you can add any other property.

Key	ValueType	Default	Combination	Description	Example
ignore	bool	true	Override		ignore = false
confidential	bool	false	Override		confidential = true
modelFileExtension	Comma separated list of strings	empty	Override		modelFileExtension = sct
traceFileExtension	Comma separated list of strings	empty	Override		traceFileExtension = eso, .trace
resourceSetID	String	null	Not propagated	confidential	Boolean		propertiesresourceSetID = my-unique-id
modelProperties	Comma separated list of strings	empty			modelProperties = tiny-model, broken
properties		empty	Combined
name
complexityreferences
Other properties

Note that ignore is true by default, that means you have to set it explicitly to include new files/folders in the automatic testing process.

Benchmarks