bohl@itemis.de
d2a5eeb3ce
repaired generator for c/cpp string compare, added new generated tests in C / C++
|
il y a 10 ans | |
|---|---|---|
| .. | ||
| .settings | il y a 10 ans | |
| META-INF | il y a 10 ans | |
| gtests | il y a 10 ans | |
| model | il y a 10 ans | |
| scripts | il y a 13 ans | |
| src | il y a 10 ans | |
| test-gen | il y a 10 ans | |
| .classpath | il y a 10 ans | |
| .project | il y a 12 ans | |
| README | il y a 13 ans | |
| build.properties | il y a 12 ans | |
| pom.xml | il y a 10 ans | |
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.
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.