Difference between revisions of "Googletest"
(add initial googletest page) |
|||
| Line 2: | Line 2: | ||
What googletest (gtest) is and a general introduction how to use it can be found on the [https://code.google.com/p/googletest/ googletest] webpage. The [https://code.google.com/p/googletest/wiki/Documentation documentation] is very useful and provide some good examples, starting with a primer up to more comprehensive documentation for complex test. | What googletest (gtest) is and a general introduction how to use it can be found on the [https://code.google.com/p/googletest/ googletest] webpage. The [https://code.google.com/p/googletest/wiki/Documentation documentation] is very useful and provide some good examples, starting with a primer up to more comprehensive documentation for complex test. | ||
| + | |||
| + | Unit tests will be enabled by default in the future but can be disabled during '''configure'''. Simply add the '''--disable-unit-tests''' to your configure command. | ||
| + | |||
| + | |||
| + | ==How to use gtest== | ||
| + | gtest is not yet fully integrated in gbuild but available in dmake makefiles. If we will continue with gbuild a better and direct integration have to be provided. But for now you can easy use with a dmake file. Up to 9 run unit test targets are supported and you can easy enable or disable the execution of one test. | ||
| + | For example a simple makefile can look like this: | ||
| + | <source lang="java"> | ||
| + | PRJ = .. | ||
| + | PRJNAME = sal | ||
| + | TARGET = salunittest | ||
| + | |||
| + | ENABLE_EXCEPTIONS = TRUE | ||
| + | |||
| + | .INCLUDE: settings.mk | ||
| + | |||
| + | .IF "$(ENABLE_UNIT_TESTS)" != "YES" | ||
| + | all: | ||
| + | @echo unit tests are disabled. Nothing to do. | ||
| + | |||
| + | .ELSE | ||
| + | |||
| + | xOBJFILES = $(APP1OBJS) | ||
| + | |||
| + | APP1OBJS = $(OBJ)/unittest.obj | ||
| + | APP1RPATH = NONE | ||
| + | APP1STDLIBS = $(GTESTLIB) $(SALLIB) | ||
| + | APP1TARGET = salunittest | ||
| + | APP1TEST = enabled | ||
| + | #APP1TEST = disabled | ||
| + | |||
| + | .INCLUDE: target.mk | ||
| + | |||
| + | .ENDIF | ||
| + | </source> | ||
| + | |||
| + | The whole test (directory) gets build only if unit tests are not disabled globally during configure. If you have several test binaries in one directory you can easy disable the execution of one test by setting the variable '''APP1TEST=disable''' | ||
Revision as of 11:08, 30 May 2014
googletest is Google's framework for writing C++ tests (unit tests) on a variety of platforms. The intention is to use this test framework as replacement for cppunit that is license incompatible with Apache.
What googletest (gtest) is and a general introduction how to use it can be found on the googletest webpage. The documentation is very useful and provide some good examples, starting with a primer up to more comprehensive documentation for complex test.
Unit tests will be enabled by default in the future but can be disabled during configure. Simply add the --disable-unit-tests to your configure command.
How to use gtest
gtest is not yet fully integrated in gbuild but available in dmake makefiles. If we will continue with gbuild a better and direct integration have to be provided. But for now you can easy use with a dmake file. Up to 9 run unit test targets are supported and you can easy enable or disable the execution of one test. For example a simple makefile can look like this:
PRJ = ..
PRJNAME = sal
TARGET = salunittest
ENABLE_EXCEPTIONS = TRUE
.INCLUDE: settings.mk
.IF "$(ENABLE_UNIT_TESTS)" != "YES"
all:
@echo unit tests are disabled. Nothing to do.
.ELSE
xOBJFILES = $(APP1OBJS)
APP1OBJS = $(OBJ)/unittest.obj
APP1RPATH = NONE
APP1STDLIBS = $(GTESTLIB) $(SALLIB)
APP1TARGET = salunittest
APP1TEST = enabled
#APP1TEST = disabled
.INCLUDE: target.mk
.ENDIF
The whole test (directory) gets build only if unit tests are not disabled globally during configure. If you have several test binaries in one directory you can easy disable the execution of one test by setting the variable APP1TEST=disable
