20,741
edits
FlightGear Headless: Difference between revisions
→Regression Testing in FlightGear
| Line 154: | Line 154: | ||
== Regression Testing in FlightGear == | == Regression Testing in FlightGear == | ||
{{FGCquote | |||
|1= the intel driver is more strict on these and throws errors when others are happily moving along, so that got me into thinking whether we could somehow wire the shader compiler into Jenkins to have these checked right away? Just like it's useful in catching compilation errors on windows and mac, that are less common architectures among the developers. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/34857657/ | |||
| title = <nowiki>Re: [Flightgear-devel] To Release or not?</nowiki> | |||
| author = <nowiki>Tuomas Kuosmanen</nowiki> | |||
| date = Feb 17th, 2016 | |||
| added = Feb 17th, 2016 | |||
| script_version = 0.25 | |||
}} | |||
}} | |||
While introducing unit tests and regression tests into the FlightGear project has been repeatedly brought up by several long-term contributors [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg12321.html] and core developers [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg11825.html], it isn't yet in wide or regular use in FlightGear, even though it is generally understood to be a worthwhile addition to FlightGear in order to do automated testing of individual features, for example when preparing releases [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg11832.html]. | While introducing unit tests and regression tests into the FlightGear project has been repeatedly brought up by several long-term contributors [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg12321.html] and core developers [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg11825.html], it isn't yet in wide or regular use in FlightGear, even though it is generally understood to be a worthwhile addition to FlightGear in order to do automated testing of individual features, for example when preparing releases [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg11832.html]. | ||