Browse Source

ensure desired gtest directory is first include dir to avoid problems with coexisting default installs (especially ancient ones ;)

beacon_test
parent
commit
bc671fef83
2 changed files with 9 additions and 6 deletions
  1. +2
    -2
      test/Makefile
  2. +7
    -4
      test/README.md

+ 2
- 2
test/Makefile View File

@ -52,10 +52,10 @@ else ifeq ($(OPENPGP),NETPGP)
endif
endif
CXXFLAGS:=$(filter-out -DNDEBUG,$(CXXFLAGS))
CXXFLAGS:=-I$(GTEST_INC_DIR) $(filter-out -DNDEBUG,$(CXXFLAGS))
# FIXME Possibly missing incdirs: ASN1C_INC
CXXFLAGS+= -I./src -I../sync $(CPPUNIT_INC) $(INC_FLAGS) -I$(GTEST_INC_DIR) -Wno-deprecated
CXXFLAGS+= -I./src -I../sync $(CPPUNIT_INC) $(INC_FLAGS) -Wno-deprecated
ifeq ($(OPENPGP),GPG)
CXXFLAGS+= -DUSE_GPG $(GPGME_INC)


+ 7
- 4
test/README.md View File

@ -43,15 +43,18 @@ Presuming the above works, then from the top test directory, simply run make.
# Running the Engine Test Suite
If you simply want to run the suite and see what tests fail, either:
## To simply run the test suite and see what tests fail...
Do one of:
1. make test OR
2. python3 \<path to gtest-parallel.py\> ./EngineTests
To run individual tests, especially for debugging purposes:
## To run individual test suites, especially for debugging purposes
1. Blah, and, for example,
2. {lldb ./EngineTests some-blah-args-here}
1. To run sequentially, IN THE SAME PROCESS: ./EngineTests TestSuiteName* (for example, for DeleteKeyTest: ./EngineTests DeleteKeyTest*)
2. To debug the same: lldb ./EngineTests TestSuiteName*
3. To run sequentially IN DIFFERENT PROCESSES: (FIXME - is this really the case?)
# Creating new tests


Loading…
Cancel
Save