20,741
edits
m (→Structure: https://sourceforge.net/p/flightgear/mailman/message/35801322/) |
|||
Line 127: | Line 127: | ||
== Getting involved == | == Getting involved == | ||
{{Out of date}} | |||
We would recommend copying existing tests in SimGear or more recently, FlightGear - we have a few. | We would recommend copying existing tests in SimGear or more recently, FlightGear - we have a few. | ||
Line 136: | Line 138: | ||
For Yasim and FDM/Yasim/tests dir might make sense <ref>https://sourceforge.net/p/flightgear/mailman/message/35801322/</ref> | For Yasim and FDM/Yasim/tests dir might make sense <ref>https://sourceforge.net/p/flightgear/mailman/message/35801322/</ref> | ||
The SimGear test macros are in <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35804333/ | |||
|title = <nowiki> Re: [Flightgear-devel] How to test C++ code 'automatically'? </nowiki> | |||
|author = <nowiki> Florent Rougon </nowiki> | |||
|date = Apr 24th, 2017 | |||
|added = Apr 24th, 2017 | |||
|script_version = 0.36 | |||
}}</ref> | |||
: | |||
https://sourceforge.net/p/flightgear/simgear/ci/next/tree/simgear/misc/test_macros.hxx | |||
For usage example, just look at one of the many *_test.cxx modules in | |||
SimGear (except those still using boost test macros), for instance: | |||
https://sourceforge.net/p/flightgear/simgear/ci/next/tree/simgear/misc/strutils_test.cxx | |||
https://sourceforge.net/p/flightgear/simgear/ci/next/tree/simgear/misc/argparse_test.cxx | |||
https://sourceforge.net/p/flightgear/simgear/ci/next/tree/simgear/io/iostreams/zlibstream_test.cxx | |||
For the FG testing framework: it has been only very recently integrated | |||
(and I believe is currently disabled on jenkins because the tests failed | |||
there for a still-unknown reason), I haven't used it myself, and Edward | |||
wrote a description of his work here: | |||
https://sourceforge.net/p/flightgear/mailman/message/35661026/ | |||
== New SubSystem Design == | == New SubSystem Design == |