Andreas Mülder 949ae92423 incremented to 3.3.1 (#2017) 7 lat temu
..
.settings 20066e1e9d Newly Generated C Tests after the Changing of the Test File Naming 8 lat temu
META-INF 949ae92423 incremented to 3.3.1 (#2017) 7 lat temu
gtests 94444b41ff Updated tests for local event handling in event driven case - Issue 1981 (#1986) 7 lat temu
libraryTarget a35bceb258 newly generated C tests with less code 8 lat temu
model 94444b41ff Updated tests for local event handling in event driven case - Issue 1981 (#1986) 7 lat temu
scripts 34155c0004 Testcase for C added 13 lat temu
src 98a6fb64da Add a test for 'statemachinePrefix' behavior 7 lat temu
test-gen 94444b41ff Updated tests for local event handling in event driven case - Issue 1981 (#1986) 7 lat temu
.classpath 65e7315531 Java se 1.8 (#1452) 8 lat temu
.gitignore 3c6eb975b0 Added .gitignore files 10 lat temu
.project fa17e75d27 version upgrade to 2.1.2 12 lat temu
README 55fe8524c5 Add setup instructions for C tests 13 lat temu
all C generator tests.launch 3fa52bde0d Enable validation also for generator tests (#1487) 8 lat temu
build.properties ddd124e9f7 Added AllTests for generator.c.test 12 lat temu
log4j.properties b7343ae0af Add ITypeSystemAccess for TypeSpecifier #975 (#976) 9 lat temu
pom.xml 949ae92423 incremented to 3.3.1 (#2017) 7 lat temu

README

Executing the C tests.

Preconditions:

In order to run the C test the google test framework (gtest) must be installed.

To locate the required gtest headers and libraries the environment variable 'GTEST_DIR' is used.
This directory has to contain the 'gtest' and 'gtest_main' libs as well as the folder 'includes'
that has to contain the required header files.

If no environment variable is set then the test try to find the headers at the default systems header and library locations.

Please consult the gtest documentation for installation and build instructions (cmake based build seems to fit best).



Running the tests:

The C tests are wrapped by Junit tests. Simply run these as Junit-Plugin tests and make sure that the PermGenSpace is big enough ( -XX:MaxPermSize=256m ).

Running as plugin tests is necessary since several resources required for the test are loaded from the plugin bundle.