2,561
edits
FlightGear Headless: Difference between revisions
m
→Regression Testing in FlightGear
m (→Background) |
|||
| Line 14: | Line 14: | ||
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). | 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]). | 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] or [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23521.html]). | ||
These obstacles in debugging such highly specific issues are also highlighted by core developers to severely limit the troubleshooting process | These obstacles in debugging such highly specific issues are also highlighted by core developers to severely limit the troubleshooting process | ||