Cppunit effort

961 bytes added, 19:19, 2 April 2018
The long term assumption here is that one day we will have significant test coverage of both fgfs and fgdata, and that running a full set of tests would take a significant amount of time (say 30 min to 1 hour). The idea was that this could be run on a [[FlightGear Build Server|Jenkins VM]], or a similar system, triggered in the same way Gene's Jenkins set up is currently run, i.e. "Started by an SCM change". If run on Jenkins, then it could either be run together with the flightgear build or as a separate project (with "flightgear" set as an upstream project). This would help identify who accidentally broke what.<ref>{{cite web
|url =
|title = <nowiki> [Flightgear-devel] RFC: Working on a testing strategy for
FlightGear. </nowiki>
|author = <nowiki> Edward d'Auvergne </nowiki>
|date = Mar 5th, 2018
|added = Mar 5th, 2018
|script_version = 0.36
== Motivation ==