fly/flightgear
1
0
Fork 0
Code Activity
flightgear/test_suite/CMakeLists.txt

174 lines
6.3 KiB
Text
Raw Normal View History

CMake: Shifted the target setup code into its own CMake module. This is for simplifying the main src/Main/CMakeLists.txt file and allowing the code to be shared with the test suite.
2018-03-25 12:18:24 +00:00
# CMake module includes.
CMake: Shifted the FlightGear embedded resources code into its own CMake module. This is for simplifying the main src/Main/CMakeLists.txt file and allowing the code to be shared with the test suite. The generated source and header files have also been removed from the main source list and placed in the CMake module as the global variables EMBEDDED_RESOURCE_SOURCES and EMBEDDED_RESOURCE_HEADERS.
2018-03-25 12:29:02 +00:00
include(SetupFGFSEmbeddedResources)
CMake: Split the target links and includes into separate CMake modules.
2018-03-26 20:27:25 +00:00
include(SetupFGFSIncludes)
CMake: Shifted the target setup code into its own CMake module. This is for simplifying the main src/Main/CMakeLists.txt file and allowing the code to be shared with the test suite.
2018-03-25 12:18:24 +00:00
include(SetupFGFSLibraries)
CMake: Shifted the MSVC grouping code into its own CMake module. This is for simplifying the main src/Main/CMakeLists.txt file and allowing the code to be shared with the test suite.
2018-03-25 12:35:46 +00:00
include(SetupMSVCGrouping)
CMake: Shifted the target setup code into its own CMake module. This is for simplifying the main src/Main/CMakeLists.txt file and allowing the code to be shared with the test suite.
2018-03-25 12:18:24 +00:00
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
# Add each test suite category.
foreach(test_category
gui_tests
simgear_tests
system_tests
unit_tests
TestSuite: Added a testing category for FGData.
2019-09-13 09:51:20 +00:00
fgdata_tests
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
)
add_subdirectory(${test_category})
endforeach(test_category)
TestSuite: Implementation of FGTestApi. The test_suite/helpers directory has been renamed to test_suite/FGTestApi/ and all the fgtest namespaces renamed to FGTestApi. The helper functions are now also placed into either a setUp or tearDown namespace depending on their function. And a new FGTestApi::PrivateAccessor::FDM namespace has been created for holding friend classes used to access private or protected variables or functions from solely within the test suite.
2018-07-16 13:59:21 +00:00
# Add the testing API.
add_subdirectory(FGTestApi)
TestSuite: Shift of the globals unit test helper functions into the test suite. The setting of the SG log levels and developer mode has been removed as this clashes with the output control set by the test suite main() function.
2018-03-13 19:56:31 +00:00
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
# Add all test suite sources and headers.
set(TESTSUITE_SOURCES
${TESTSUITE_SOURCES}
bootstrap.cxx
TestSuite: Addition of a test data store singleton. This is for currently for storing the path to FGData for use in any tests requiring it.
2018-03-28 15:30:59 +00:00
dataStore.cxx
TestSuite: Custom output formatting. A large number of improvements have been made by subclassing the CppUnit classes and overriding the base functions, including CompilerOutputter, TestListener, and TextTestRunner. All IO has also been captured by the test runner. The result is that during the test suite run, only the characters '.', 'F', and 'E' are output for a pass, failure and error state. At the end of each test suite category, all failures and errors are reported in full detail, including the different captured IO streams. A final synopsis is printed out, improving the overview in the case of too many tests failing. For the fgCompilerOutputter class, the printSuccess(), printFailureReport(), printFailureDetail(), and printSuiteStats() functions have been replaced to implement the above printout design. The class also stores the std::vector of TestIOCapt structures for the final printouts. The fgTestListener class handles the events from the running of the test suite. The startTest() and endTest() functions are used for IO capture. The IO is placed into a TestIOCapt data structure, with one std::string for holding the combined STDOUT and STDERR IO, and another for the SG_LOG IO. If failures occur, the TestIOCapt structure is appended to the fgCompilerOutputter vector. The startTest() and endTest() functions are also used for starting and stopping a timer to allow the full test suite to be timed. And the addFailure() function simply registers test failures or errors. The fgTestRunner class overrides the CppUnit::TextTestRunner::run() function, simply to prevent the base method from spawning a second test listener, causing the test output to be duplicated. Some auxiliary formatting functions have been added to print out titles, sections, and synopsis summary lines.
2016-02-09 16:34:56 +00:00
fgCompilerOutputter.cxx
fgTestListener.cxx
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
fgTestRunner.cxx
TestSuite: Custom output formatting. A large number of improvements have been made by subclassing the CppUnit classes and overriding the base functions, including CompilerOutputter, TestListener, and TextTestRunner. All IO has also been captured by the test runner. The result is that during the test suite run, only the characters '.', 'F', and 'E' are output for a pass, failure and error state. At the end of each test suite category, all failures and errors are reported in full detail, including the different captured IO streams. A final synopsis is printed out, improving the overview in the case of too many tests failing. For the fgCompilerOutputter class, the printSuccess(), printFailureReport(), printFailureDetail(), and printSuiteStats() functions have been replaced to implement the above printout design. The class also stores the std::vector of TestIOCapt structures for the final printouts. The fgTestListener class handles the events from the running of the test suite. The startTest() and endTest() functions are used for IO capture. The IO is placed into a TestIOCapt data structure, with one std::string for holding the combined STDOUT and STDERR IO, and another for the SG_LOG IO. If failures occur, the TestIOCapt structure is appended to the fgCompilerOutputter vector. The startTest() and endTest() functions are also used for starting and stopping a timer to allow the full test suite to be timed. And the addFailure() function simply registers test failures or errors. The fgTestRunner class overrides the CppUnit::TextTestRunner::run() function, simply to prevent the base method from spawning a second test listener, causing the test output to be duplicated. Some auxiliary formatting functions have been added to print out titles, sections, and synopsis summary lines.
2016-02-09 16:34:56 +00:00
formatting.cxx
TestSuite: Capture and reporting of all simgear logstream priorities. Each of the global logstream priorities are captured into its own std::ostringstream stream, all held together in the test suite global _iostreams class instance. This object can be obtained by calling getIOstreams(). The streams are captured using the StreamLogCallback class, which is a simple modification of the simgear FileLogCallback class, registered with the global logstream's addCallback() function. When tests fail, all of contents the different simgear logstreams are now reported. The failure report consists of the following sections: - Failure information. - SG_BULK simgear logstream (all messages). - SG_BULK only simgear logstream. - SG_DEBUG only simgear logstream. - SG_INFO only simgear logstream. - SG_WARN only simgear logstream. - SG_ALERT only simgear logstream. - Combined STDOUT and STDERR streams. Any empty sections, except for SG_BULK, will not be shown.
2016-02-12 18:42:20 +00:00
logging.cxx
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
testSuite.cxx
)
set(TESTSUITE_HEADERS
${TESTSUITE_HEADERS}
TestSuite: Addition of a test data store singleton. This is for currently for storing the path to FGData for use in any tests requiring it.
2018-03-28 15:30:59 +00:00
dataStore.hxx
TestSuite: Custom output formatting. A large number of improvements have been made by subclassing the CppUnit classes and overriding the base functions, including CompilerOutputter, TestListener, and TextTestRunner. All IO has also been captured by the test runner. The result is that during the test suite run, only the characters '.', 'F', and 'E' are output for a pass, failure and error state. At the end of each test suite category, all failures and errors are reported in full detail, including the different captured IO streams. A final synopsis is printed out, improving the overview in the case of too many tests failing. For the fgCompilerOutputter class, the printSuccess(), printFailureReport(), printFailureDetail(), and printSuiteStats() functions have been replaced to implement the above printout design. The class also stores the std::vector of TestIOCapt structures for the final printouts. The fgTestListener class handles the events from the running of the test suite. The startTest() and endTest() functions are used for IO capture. The IO is placed into a TestIOCapt data structure, with one std::string for holding the combined STDOUT and STDERR IO, and another for the SG_LOG IO. If failures occur, the TestIOCapt structure is appended to the fgCompilerOutputter vector. The startTest() and endTest() functions are also used for starting and stopping a timer to allow the full test suite to be timed. And the addFailure() function simply registers test failures or errors. The fgTestRunner class overrides the CppUnit::TextTestRunner::run() function, simply to prevent the base method from spawning a second test listener, causing the test output to be duplicated. Some auxiliary formatting functions have been added to print out titles, sections, and synopsis summary lines.
2016-02-09 16:34:56 +00:00
fgCompilerOutputter.hxx
fgTestListener.hxx
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
fgTestRunner.hxx
TestSuite: Custom output formatting. A large number of improvements have been made by subclassing the CppUnit classes and overriding the base functions, including CompilerOutputter, TestListener, and TextTestRunner. All IO has also been captured by the test runner. The result is that during the test suite run, only the characters '.', 'F', and 'E' are output for a pass, failure and error state. At the end of each test suite category, all failures and errors are reported in full detail, including the different captured IO streams. A final synopsis is printed out, improving the overview in the case of too many tests failing. For the fgCompilerOutputter class, the printSuccess(), printFailureReport(), printFailureDetail(), and printSuiteStats() functions have been replaced to implement the above printout design. The class also stores the std::vector of TestIOCapt structures for the final printouts. The fgTestListener class handles the events from the running of the test suite. The startTest() and endTest() functions are used for IO capture. The IO is placed into a TestIOCapt data structure, with one std::string for holding the combined STDOUT and STDERR IO, and another for the SG_LOG IO. If failures occur, the TestIOCapt structure is appended to the fgCompilerOutputter vector. The startTest() and endTest() functions are also used for starting and stopping a timer to allow the full test suite to be timed. And the addFailure() function simply registers test failures or errors. The fgTestRunner class overrides the CppUnit::TextTestRunner::run() function, simply to prevent the base method from spawning a second test listener, causing the test output to be duplicated. Some auxiliary formatting functions have been added to print out titles, sections, and synopsis summary lines.
2016-02-09 16:34:56 +00:00
formatting.hxx
TestSuite: Capture and reporting of all simgear logstream priorities. Each of the global logstream priorities are captured into its own std::ostringstream stream, all held together in the test suite global _iostreams class instance. This object can be obtained by calling getIOstreams(). The streams are captured using the StreamLogCallback class, which is a simple modification of the simgear FileLogCallback class, registered with the global logstream's addCallback() function. When tests fail, all of contents the different simgear logstreams are now reported. The failure report consists of the following sections: - Failure information. - SG_BULK simgear logstream (all messages). - SG_BULK only simgear logstream. - SG_DEBUG only simgear logstream. - SG_INFO only simgear logstream. - SG_WARN only simgear logstream. - SG_ALERT only simgear logstream. - Combined STDOUT and STDERR streams. Any empty sections, except for SG_BULK, will not be shown.
2016-02-12 18:42:20 +00:00
logging.hxx
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
)
# The test suite output directory.
set(TESTSUITE_OUTPUT_DIR "${CMAKE_CURRENT_BINARY_DIR}")
TestSuite: Support for building the FlightGear bundled CppUnit library. The CppUnit source is built as a static library and linked to the run_test_suite executable. The FlightGear CppUnit library is now build using CMake rather than using the Autotools build system.
2018-03-06 10:08:15 +00:00
# Get the CppUnit sources and headers to be built into the test suite.
if (NOT SYSTEM_CPPUNIT)
message(STATUS "CppUnit: Building the FlightGear supplied CppUnit library")
get_property(CPPUNIT_SOURCES GLOBAL PROPERTY CPPUNIT_SOURCES)
get_property(CPPUNIT_HEADERS GLOBAL PROPERTY CPPUNIT_HEADERS)
add_library(CppUnitLib STATIC ${CPPUNIT_SOURCES} ${CPPUNIT_HEADERS})
Code changes for crash reporting with Sentry.
2020-04-07 08:38:54 +00:00
target_include_directories(CppUnitLib PUBLIC "${PROJECT_SOURCE_DIR}/3rdparty/cppunit/include")
TestSuite: Support for building the FlightGear bundled CppUnit library. The CppUnit source is built as a static library and linked to the run_test_suite executable. The FlightGear CppUnit library is now build using CMake rather than using the Autotools build system.
2018-03-06 10:08:15 +00:00
set(CPPUNIT_LIBRARIES CppUnitLib)
else()
message(STATUS "CppUnit: Linking to the system supplied CppUnit library")
endif()
TestSuite: CTest support for running each test suite as a separate ctest. The --ctest command line option has also been added to allow for a simplified output from the test suite more suitable for the ctest verbose output.
2018-03-12 10:43:24 +00:00
#-----------------------------------------------------------------------------
# Set up all test suites as CTests.
TestSuite: Elimination of the now unused ENABLE_TESTS CMake variable.
2018-06-11 09:39:57 +00:00
# Activation.
include(Dart)
TestSuite: CTest support for running each test suite as a separate ctest. The --ctest command line option has also been added to allow for a simplified output from the test suite more suitable for the ctest verbose output.
2018-03-12 10:43:24 +00:00
# System test suites.
TestSuite: Renamed the run_test_suite binary to fgfs_test_suite. This is on James' suggestion. The 'fgfs_test_suite' or 'fgfs_test_suite.exe' binary file name is significantly more obvious as to its purpose.
2019-09-25 12:50:34 +00:00
add_test(AeroMeshSystemTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -s AeroMeshTests)
#add_test(GPSSystemTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -s GPSTests)
#add_test(NavaidsSystemTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -s NavaidsTests)
TestSuite: CTest support for running each test suite as a separate ctest. The --ctest command line option has also been added to allow for a simplified output from the test suite more suitable for the ctest verbose output.
2018-03-12 10:43:24 +00:00
# Unit test suites.
TestSuite: Renamed the run_test_suite binary to fgfs_test_suite. This is on James' suggestion. The 'fgfs_test_suite' or 'fgfs_test_suite.exe' binary file name is significantly more obvious as to its purpose.
2019-09-25 12:50:34 +00:00
add_test(AddonManagementUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u AddonManagementTests)
add_test(AeroElementUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u AeroElementTests)
TestSuite: Support for running more of the tests via CTest.
2019-11-07 09:01:35 +00:00
add_test(AircraftPerformanceUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u AircraftPerformanceTests)
TestSuite: Renamed the run_test_suite binary to fgfs_test_suite. This is on James' suggestion. The 'fgfs_test_suite' or 'fgfs_test_suite.exe' binary file name is significantly more obvious as to its purpose.
2019-09-25 12:50:34 +00:00
add_test(AutosaveMigrationUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u AutosaveMigrationTests)
add_test(FlightplanUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u FlightplanTests)
TestSuite: All tests can now be run via CTest again.
2020-04-24 20:52:24 +00:00
add_test(FPNasalUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u FPNasalTests)
TestSuite: Support for running more of the tests via CTest.
2019-11-07 09:01:35 +00:00
add_test(GPSUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u GPSTests)
add_test(HoldControllerUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u HoldControllerTests)
TestSuite: Migration of the HIDInput tests to the CppUnit framework. The extractBits(), signExtend(), and writeBits() functions of the anonymous namespace in Input/FGHIDEventInput.cxx have been shifted out of the namespace and are now exposed via the header. This is needed as <Input/FGHIDEventInput.cxx> cannot be imported within the CppUnit infrastructure, as it is already built into the run_test_suite binary.
2018-06-14 07:32:02 +00:00
if(ENABLE_HID_INPUT)
TestSuite: Renamed the run_test_suite binary to fgfs_test_suite. This is on James' suggestion. The 'fgfs_test_suite' or 'fgfs_test_suite.exe' binary file name is significantly more obvious as to its purpose.
2019-09-25 12:50:34 +00:00
add_test(HIDInputUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u HIDInputTests)
TestSuite: Migration of the HIDInput tests to the CppUnit framework. The extractBits(), signExtend(), and writeBits() functions of the anonymous namespace in Input/FGHIDEventInput.cxx have been shifted out of the namespace and are now exposed via the header. This is needed as <Input/FGHIDEventInput.cxx> cannot be imported within the CppUnit infrastructure, as it is already built into the run_test_suite binary.
2018-06-14 07:32:02 +00:00
endif()
TestSuite: Renamed the run_test_suite binary to fgfs_test_suite. This is on James' suggestion. The 'fgfs_test_suite' or 'fgfs_test_suite.exe' binary file name is significantly more obvious as to its purpose.
2019-09-25 12:50:34 +00:00
add_test(LaRCSimMatrixUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u LaRCSimMatrixTests)
add_test(MktimeUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u MktimeTests)
add_test(NasalSysUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u NasalSysTests)
add_test(NavaidsUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u NavaidsTests)
TestSuite: Support for running more of the tests via CTest.
2019-11-07 09:01:35 +00:00
add_test(NavRadioUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u NavRadioTests)
TestSuite: Renamed the run_test_suite binary to fgfs_test_suite. This is on James' suggestion. The 'fgfs_test_suite' or 'fgfs_test_suite.exe' binary file name is significantly more obvious as to its purpose.
2019-09-25 12:50:34 +00:00
add_test(PosInitUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u PosInitTests)
TestSuite: Support for running more of the tests via CTest.
2019-11-07 09:01:35 +00:00
add_test(RNAVProcedureUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u RNAVProcedureTests)
add_test(RouteManagerUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u RouteManagerTests)
TestSuite: Renamed the run_test_suite binary to fgfs_test_suite. This is on James' suggestion. The 'fgfs_test_suite' or 'fgfs_test_suite.exe' binary file name is significantly more obvious as to its purpose.
2019-09-25 12:50:34 +00:00
add_test(YASimAtmosphereUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -u YASimAtmosphereTests)
TestSuite: CTest support for running each test suite as a separate ctest. The --ctest command line option has also been added to allow for a simplified output from the test suite more suitable for the ctest verbose output.
2018-03-12 10:43:24 +00:00
# GUI test suites.
# Simgear unit test suites.
TestSuite: Fix for the running the CanvasTests as CTests. These are in the simgear unit test category, not the normal unit test category.
2020-04-27 19:29:56 +00:00
add_test(CanvasSimgearUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -m CanvasTests)
TestSuite: Renamed the run_test_suite binary to fgfs_test_suite. This is on James' suggestion. The 'fgfs_test_suite' or 'fgfs_test_suite.exe' binary file name is significantly more obvious as to its purpose.
2019-09-25 12:50:34 +00:00
add_test(MathGeodesySimgearUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -m MathGeodesyTests)
add_test(SimgearPropsSimgearUnitTests ${TESTSUITE_OUTPUT_DIR}/fgfs_test_suite --ctest -m SimgearPropsTests)
TestSuite: CTest support for running each test suite as a separate ctest. The --ctest command line option has also been added to allow for a simplified output from the test suite more suitable for the ctest verbose output.
2018-03-12 10:43:24 +00:00
TestSuite: Added a testing category for FGData.
2019-09-13 09:51:20 +00:00
# FGData test suites.
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
#-----------------------------------------------------------------------------
TestSuite: Comment rewording as the CMake file is no longer a copy from Main.
2018-03-25 12:45:29 +00:00
# Set up the binary.
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
CMake: Shifted the FlightGear embedded resources code into its own CMake module. This is for simplifying the main src/Main/CMakeLists.txt file and allowing the code to be shared with the test suite. The generated source and header files have also been removed from the main source list and placed in the CMake module as the global variables EMBEDDED_RESOURCE_SOURCES and EMBEDDED_RESOURCE_HEADERS.
2018-03-25 12:29:02 +00:00
# Set up the embedded resources.
setup_fgfs_embedded_resources()
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
CMake: Shifted the MSVC grouping code into its own CMake module. This is for simplifying the main src/Main/CMakeLists.txt file and allowing the code to be shared with the test suite.
2018-03-25 12:35:46 +00:00
# Sort the sources and headers for MSVC.
setup_msvc_grouping()
Switch test_suite build to use an OBJECT library Remove use of BUILDING_TESTSUITE from headers. Where possible, move test APIs to their own file in the test_suite dir (testApis.cxx). For some others, add them to a special list of ‘sources which depend on the build mode’. This will hopefully go away with some further refactoring.
2021-03-08 16:44:42 +00:00
# most object files come from fgfsObjects target: this property
# contains all the sources which need to be compiled seperately
# for the test-suite, becuase they depend on BUILDING_TESTSUTIE define
# we setup below via target_compile_definitions
Improve CMake strucutre
2020-08-19 13:49:50 +00:00
Switch test_suite build to use an OBJECT library Remove use of BUILDING_TESTSUITE from headers. Where possible, move test APIs to their own file in the test_suite dir (testApis.cxx). For some others, add them to a special list of ‘sources which depend on the build mode’. This will hopefully go away with some further refactoring.
2021-03-08 16:44:42 +00:00
get_property(TEST_SOURCES GLOBAL PROPERTY FG_TEST_SOURCES)
Embedded Resources: Fix for Ninja 1.9 Refactor to break circular references. New custom target generates the resource files. FGFS and Test_Suite targets declare a dependency to the generated files.
2019-12-26 07:26:44 +00:00
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
# Set up the separate executable for running the test suite.
TestSuite: Renamed the run_test_suite binary to fgfs_test_suite. This is on James' suggestion. The 'fgfs_test_suite' or 'fgfs_test_suite.exe' binary file name is significantly more obvious as to its purpose.
2019-09-25 12:50:34 +00:00
add_executable(fgfs_test_suite
Switch test_suite build to use an OBJECT library Remove use of BUILDING_TESTSUITE from headers. Where possible, move test APIs to their own file in the test_suite dir (testApis.cxx). For some others, add them to a special list of ‘sources which depend on the build mode’. This will hopefully go away with some further refactoring.
2021-03-08 16:44:42 +00:00
${TEST_SOURCES}
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
${TESTSUITE_SOURCES}
${TESTSUITE_HEADERS}
Switch test_suite build to use an OBJECT library Remove use of BUILDING_TESTSUITE from headers. Where possible, move test APIs to their own file in the test_suite dir (testApis.cxx). For some others, add them to a special list of ‘sources which depend on the build mode’. This will hopefully go away with some further refactoring.
2021-03-08 16:44:42 +00:00
$<TARGET_OBJECTS:fgfsObjects>
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
)
Embedded Resources: Fix for Ninja 1.9 Refactor to break circular references. New custom target generates the resource files. FGFS and Test_Suite targets declare a dependency to the generated files.
2019-12-26 07:26:44 +00:00
Embedded resources: better cmake command Use add_custom_command and an intermediate OBJECT library to avoid rerunning fgrcc unless the XML input file has actually changed.
2020-08-21 11:13:10 +00:00
add_dependencies(fgfs_test_suite buildId)
TestSuite: Renamed the run_test_suite binary to fgfs_test_suite. This is on James' suggestion. The 'fgfs_test_suite' or 'fgfs_test_suite.exe' binary file name is significantly more obvious as to its purpose.
2019-09-25 12:50:34 +00:00
set_target_properties(fgfs_test_suite
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
PROPERTIES
RUNTIME_OUTPUT_DIRECTORY "${TESTSUITE_OUTPUT_DIR}"
)
TestSuite: CMake fix for variables missing from the parent scope. The test suite CMake target variables have been shifted back into test_suite/CMakeLists.txt. These are now correctly constructed and placed into the parent scope where the test_suite target now resides.
2019-09-25 08:38:19 +00:00
if(ENABLE_AUTOTESTING)
TestSuite: Reactivation of the ENABLE_AUTOTESTING CMake variable. This was accidentally disabled by 22de9d30b518646894ac190cc6b04371daa6d5c2.
2020-01-09 11:37:57 +00:00
set(TEST_SUITE_COMMAND "fgfs_test_suite")
Make the test_suite happier under MSBuild/VS Use the CMake target as the command to invoke, so various things get set automatically, and set the MSVCIDE_RUN_PATH so DLLs are found correctly.
2019-09-26 12:00:23 +00:00
set(TEST_SUITE_COMMENT "Running the full FlightGear test suite")
TestSuite: CMake fix for variables missing from the parent scope. The test suite CMake target variables have been shifted back into test_suite/CMakeLists.txt. These are now correctly constructed and placed into the parent scope where the test_suite target now resides.
2019-09-25 08:38:19 +00:00
else()
set(TEST_SUITE_COMMENT "Building the FlightGear test suite.")
endif(ENABLE_AUTOTESTING)
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
CMake: Split the target links and includes into separate CMake modules.
2018-03-26 20:27:25 +00:00
# Set up the target links.
TestSuite: Renamed the run_test_suite binary to fgfs_test_suite. This is on James' suggestion. The 'fgfs_test_suite' or 'fgfs_test_suite.exe' binary file name is significantly more obvious as to its purpose.
2019-09-25 12:50:34 +00:00
setup_fgfs_libraries(fgfs_test_suite)
Improve CMake strucutre
2020-08-19 13:49:50 +00:00
# Additional search paths for includes.
setup_fgfs_includes(fgfs_test_suite)
TestSuite: Initial support for a FlightGear test suite based on CppUnit. This includes the basic CMake infrastructure for building and executing the test suite. Four test categories have been added - unit, system/functional, GUI, and simgear unit tests. The test suite is run by typing 'make test_suite'. All of the fgfs sources are included in the new run_test_suite executable, excluding the bootstrap routine and its main() function. The test suite currently consists of a single dummy unit test for the NasalSys subsystem, and a single demonstration simgear/props unit test.
2016-01-28 15:56:10 +00:00
Cmake: fix some issues Scott spotted.
2020-08-23 17:12:16 +00:00
# test codce includes its headers as test_suite/foo.h, so we need this
target_include_directories(fgfs_test_suite PUBLIC ${PROJECT_SOURCE_DIR})
Code changes for crash reporting with Sentry.
2020-04-07 08:38:54 +00:00
target_compile_definitions(fgfs_test_suite PUBLIC BUILDING_TESTSUITE)
CMake: Shifted the target setup code into its own CMake module. This is for simplifying the main src/Main/CMakeLists.txt file and allowing the code to be shared with the test suite.
2018-03-25 12:18:24 +00:00
# Additional libraries just for the test suite.
TestSuite: Renamed the run_test_suite binary to fgfs_test_suite. This is on James' suggestion. The 'fgfs_test_suite' or 'fgfs_test_suite.exe' binary file name is significantly more obvious as to its purpose.
2019-09-25 12:50:34 +00:00
target_link_libraries(fgfs_test_suite ${CPPUNIT_LIBRARIES})
Make the test_suite happier under MSBuild/VS Use the CMake target as the command to invoke, so various things get set automatically, and set the MSVCIDE_RUN_PATH so DLLs are found correctly.
2019-09-26 12:00:23 +00:00
# target to run the tests
if (MSVC)
Move Qt root path variable to top-level CMakeList
2020-06-10 16:59:09 +00:00
file(TO_NATIVE_PATH "${FG_QT_BIN_DIR}" _qt5_bin_dir_native)
CMake: overhaul how we find 3rd-party files Handle the standard windows-3rd-party setup (used by fgmeta) with no extra options, and also handle the slightly odd setup we use on Jenkins. Try to tolerate all permutations of setting MSVC_3RDPARTY_ROOT to different places in the hierarchy. We no longer try to guess Boost_INCLUDEDIR by looking at parent dirs of MSVC_3RDPARTY_ROOT, since this seemed kind of bad to me. Let’s try it and see.
2020-08-26 12:57:24 +00:00
file(TO_NATIVE_PATH "${FINAL_MSVC_3RDPARTY_DIR}/bin" _msvc_3rdparty_bin_dir)
Move Qt root path variable to top-level CMakeList
2020-06-10 16:59:09 +00:00
file(TO_NATIVE_PATH "${CMAKE_INSTALL_PREFIX}/${CMAKE_INSTALL_BINDIR}" _install_bin_dir)
Make the test_suite happier under MSBuild/VS Use the CMake target as the command to invoke, so various things get set automatically, and set the MSVCIDE_RUN_PATH so DLLs are found correctly.
2019-09-26 12:00:23 +00:00
Move Qt root path variable to top-level CMakeList
2020-06-10 16:59:09 +00:00
set(CMAKE_MSVCIDE_RUN_PATH "${_install_bin_dir};${_msvc_3rdparty_bin_dir};${_qt5_bin_dir_native}")
endif()
Make the test_suite happier under MSBuild/VS Use the CMake target as the command to invoke, so various things get set automatically, and set the MSVCIDE_RUN_PATH so DLLs are found correctly.
2019-09-26 12:00:23 +00:00
Move Qt root path variable to top-level CMakeList
2020-06-10 16:59:09 +00:00
if (FG_QT_ROOT_DIR)
# for QtPlatformHeaders
target_include_directories(fgfs_test_suite PRIVATE ${FG_QT_ROOT_DIR}/include)
Make the test_suite happier under MSBuild/VS Use the CMake target as the command to invoke, so various things get set automatically, and set the MSVCIDE_RUN_PATH so DLLs are found correctly.
2019-09-26 12:00:23 +00:00
endif()
Move Qt root path variable to top-level CMakeList
2020-06-10 16:59:09 +00:00
Make the test_suite happier under MSBuild/VS Use the CMake target as the command to invoke, so various things get set automatically, and set the MSVCIDE_RUN_PATH so DLLs are found correctly.
2019-09-26 12:00:23 +00:00
add_custom_target(test_suite
TestSuite: Reactivation of the ENABLE_AUTOTESTING CMake variable. This was accidentally disabled by 22de9d30b518646894ac190cc6b04371daa6d5c2.
2020-01-09 11:37:57 +00:00
${TEST_SUITE_COMMAND}
Make the test_suite happier under MSBuild/VS Use the CMake target as the command to invoke, so various things get set automatically, and set the MSVCIDE_RUN_PATH so DLLs are found correctly.
2019-09-26 12:00:23 +00:00
DEPENDS fgfs_test_suite
COMMENT ${TEST_SUITE_COMMENT}
)
Copy permalink