6,566
edits
Software testing: Difference between revisions
Jump to navigation
Jump to search
m
More intro.
m (→Bootstrapping completely new tests: use repo link template) |
m (More intro.) |
||
| Line 1: | Line 1: | ||
{{Note|There’s already the test_suite in flightgear/test_suite using [[Cppunit effort|CppUnit]], thanks to some hard work by [[User:Bugman|Edward]]. We need more tests written for it, submissions welcome. (Pick an area of interest)<ref>https://sourceforge.net/p/flightgear/mailman/message/36972720/</ref>}} | {{Note|There’s already the test_suite in flightgear/test_suite using [[Cppunit effort|CppUnit]], thanks to some hard work by [[User:Bugman|Edward]]. We need more tests written for it, submissions welcome. (Pick an area of interest)<ref>https://sourceforge.net/p/flightgear/mailman/message/36972720/</ref>}} | ||
The FlightGear source code and data are tested by the FlightGear developers using a number of tools. This includes automated testing via unit tests in [[SimGear]] and a full test suite with multiple test categories in the [[FlightGear Git|flightgear repository]], as well as manual in-sim testing. | The FlightGear source code and data are tested by the FlightGear developers using a number of tools. This includes automated testing via unit tests in [[SimGear]] and a full test suite with multiple test categories in the [[FlightGear Git|flightgear repository]], as well as manual in-sim testing. Writing tests is one of the best ways to jump into FlightGear development. | ||
== SimGear == | == SimGear == | ||