2,561
edits
FlightGear Headless: Difference between revisions
m
→Regression Testing in FlightGear
| Line 9: | Line 9: | ||
And while there are indeed some minor build tests provided by both, the SimGear and FlightGear projects, such test cases aren't really commonly provided our updated by developers when introducing modified or new code. | And while there are indeed some minor build tests provided by both, the SimGear and FlightGear projects, such test cases aren't really commonly provided our updated by developers when introducing modified or new code. | ||
Also, these are just low level tests for specific APIs - and do not lend themselves to be used for testing high level features. | Also, these are just low level tests for specific APIs - and do not lend themselves to be used for testing high level features. | ||
Increasingly, FlightGear users are facing issues that are highly specific to their usage of FlightGear so that it isn't directly or easily possible to reproduce certain issues without exactly reproducing possibly an entire flight including identical startup and runtime settings. | |||
This is however not only a tedious and long-winded process, but also a process that may require certain usage patterns and background information or a specific set of skills (such as for example landing a specific aircraft on an aircraft carrier). | |||
In fact, the corresponding bug reports are often fairly long winded and complicated in that they try to provide all information necessary in order to allow developers to redo a certain flight segment that resulted in an error (see for example [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg19994.html]). | |||
These obstacles in debugging such highly specific issues are also highlighted by core developers to severely limit the troubleshooting process | |||
[http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg21664.html]. | |||
== Background == | == Background == | ||