Cppunit effort: Difference between revisions
Jump to navigation
Jump to search
| Line 25: | Line 25: | ||
== Background == | == Background == | ||
== Challenges == | |||
The hardest one would be to set up and run only a small subset of subsystems and other infrastructure. But it is possible to write unit tests now. Writing a system/functional test is much more difficult but, with a bit of work, it should be possible.<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/36281748/ | |||
|title = <nowiki> Re: [Flightgear-devel] Questions about TestSuite </nowiki> | |||
|author = <nowiki> Edward d'Auvergne </nowiki> | |||
|date = Apr 1st, 2018 | |||
|added = Apr 1st, 2018 | |||
|script_version = 0.36 | |||
}}</ref> | |||
== Related == | == Related == | ||
Revision as of 16:18, 2 April 2018
| Started in | 07/2017 |
|---|---|
| Description | foo |
| Contributor(s) | Bugman |
| Status | Under active development as of 04/2018 |
| Folders | foo |
| Changelog | foo |
| This article is a stub. You can help the wiki by expanding it. |
Status
Objective
The aim is to make it very easy for people to write unit or system/functional tests for fgfs (rather than simgear), which should make it much easier for new developers to dive into the flightgear sources. A long term goal might be to have good test coverage of the whole binary so that fgfs is harder to break and is more stable.[1]
Background
Challenges
The hardest one would be to set up and run only a small subset of subsystems and other infrastructure. But it is possible to write unit tests now. Writing a system/functional test is much more difficult but, with a bit of work, it should be possible.[2]
Related
References
|