20,741
edits
FlightGear Headless: Difference between revisions
→FlightGear Headless
| Line 16: | Line 16: | ||
}} | }} | ||
}} | }} | ||
{{FGCquote | |||
|I appreciate that would require us to have a unit-testing infrastructure, and way to bring up a subset of globals and the nav-cache, in a test environment. I have made a few abortive attempts at exactly that but the sprawling nature of FGGlobals keeps defeating me.<br/> | |||
<br/> | |||
(The ability to run many tests efficiently was actually one of the smaller reasons for introducing the nav-cache, since without it any automated testing system would be horribly slow) | |||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/34113076/ | |||
|title=<nowiki>Re: [Flightgear-devel] Major problems with the AI traffic system</nowiki> | |||
|author=<nowiki>James Turner</nowiki> | |||
|date=<nowiki>2015-05-14</nowiki> | |||
}} | |||
}} | |||
{{FGCquote | {{FGCquote | ||
|I am wishing I could easily add tests for the route-path / GPS code, but anything that needs ‘globals’ is hard to test in isolation. | |I am wishing I could easily add tests for the route-path / GPS code, but anything that needs ‘globals’ is hard to test in isolation. | ||