Andreas Mülder a6ffa38cbb increment to version 3.2.0 (#1785) 7 gadi atpakaļ
..
.settings 20066e1e9d Newly Generated C Tests after the Changing of the Test File Naming 8 gadi atpakaļ
META-INF a6ffa38cbb increment to version 3.2.0 (#1785) 7 gadi atpakaļ
gtests e9295ca32b Added testcases for negative verify statements (#1756) 7 gadi atpakaļ
libraryTarget a35bceb258 newly generated C tests with less code 8 gadi atpakaļ
model b0330ad9e0 C/C++ generator using modulo operators on sc_real (double) (#1699) 7 gadi atpakaļ
scripts 34155c0004 Testcase for C added 13 gadi atpakaļ
src b0330ad9e0 C/C++ generator using modulo operators on sc_real (double) (#1699) 7 gadi atpakaļ
test-gen b0330ad9e0 C/C++ generator using modulo operators on sc_real (double) (#1699) 7 gadi atpakaļ
.classpath 65e7315531 Java se 1.8 (#1452) 8 gadi atpakaļ
.gitignore 3c6eb975b0 Added .gitignore files 10 gadi atpakaļ
.project fa17e75d27 version upgrade to 2.1.2 12 gadi atpakaļ
README 55fe8524c5 Add setup instructions for C tests 13 gadi atpakaļ
all C generator tests.launch 3fa52bde0d Enable validation also for generator tests (#1487) 8 gadi atpakaļ
build.properties ddd124e9f7 Added AllTests for generator.c.test 12 gadi atpakaļ
log4j.properties b7343ae0af Add ITypeSystemAccess for TypeSpecifier #975 (#976) 9 gadi atpakaļ
pom.xml a6ffa38cbb increment to version 3.2.0 (#1785) 7 gadi atpakaļ

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.