8,564
edits
Aircraft testing checklist: Difference between revisions
Jump to navigation
Jump to search
m
Wiki formatting
m (Wiki formatting) |
|||
| Line 1: | Line 1: | ||
This is a set of basic checks to run on an aircraft, to validate compatibility with a FlightGear version | This is a set of basic checks to run on an aircraft, to validate compatibility with a [[FlightGear]] version | ||
For aircraft in | For aircraft in [[FGAddon]] which have been claimed for testing, see the [[Aircraft tester list|tester list]] | ||
= Test | == Test procedure == | ||
Claim an aircraft, by adding your name and the aircraft to the [[ | Claim an aircraft, by adding your name and the aircraft to the [[Aircraft tester list|tester list]]. Then do a test flight going through the steps below. Then [https://sourceforge.net/p/flightgear/codetickets/new/ open a ticket] (one per aircraft!) in the tracker with any failures / issues. (You don’t need to list the things that worked, just the things that didn’t) | ||
Some important details | === Some important details === | ||
The ticket should have the following set | The ticket should have the following set | ||
| Line 13: | Line 13: | ||
* milestone=2020.2 | * milestone=2020.2 | ||
* set the label ‘aircraft-qa’ | * set the label ‘aircraft-qa’ | ||
* if the aircraft does | * if the aircraft does '''not''' have a maintainer, add a label ‘nomaintainer’ | ||
This makes it easier to find which aircraft have open issues, and which aircraft are abandoned. If the aircraft has an obvious active maintainer, it would be excellent to point them at the ticket | This makes it easier to find which aircraft have open issues, and which aircraft are abandoned. If the aircraft has an obvious active maintainer, it would be excellent to point them at the ticket | ||
General points | === General points === | ||
* avoid issues ’smaller’ than the ones on this list, broadly. If the fuel cap is in the wrong place for the 1972 model of the Piper Archer, that’s something to take up with the aircraft maintainer or learn how to fix yourself. There's no point spending hours testing such details if there is no one working on the aircraft who might fix them. | * avoid issues ’smaller’ than the ones on this list, broadly. If the fuel cap is in the wrong place for the 1972 model of the Piper Archer, that’s something to take up with the aircraft maintainer or learn how to fix yourself. There's no point spending hours testing such details if there is no one working on the aircraft who might fix them. | ||
* The list is not exhaustive: if the Harrier can’t take off vertically, or a water-bomber can’t pick up water, those are major issues for that aircraft, despite not being listed below | * The list is not exhaustive: if the Harrier can’t take off vertically, or a water-bomber can’t pick up water, those are major issues for that aircraft, despite not being listed below | ||
| Line 24: | Line 24: | ||
* If you encounter an issue which you suspect is generic to all of FlightGear, report it as normal in the tracker, or ask about it on the developer list, don't hide it inside an aircraft testing report | * If you encounter an issue which you suspect is generic to all of FlightGear, report it as normal in the tracker, or ask about it on the developer list, don't hide it inside an aircraft testing report | ||
= Metadata = | == Metadata == | ||
* does the aircraft have a clear name (not so long it overflows) | * does the aircraft have a clear name (not so long it overflows) | ||
| Line 31: | Line 31: | ||
** if it has new style-previews, do they follow the style guidelines: especially, no logos or text in them, which break readability of the splash and launcher screens. | ** if it has new style-previews, do they follow the style guidelines: especially, no logos or text in them, which break readability of the splash and launcher screens. | ||
= Basic experience = | == Basic experience == | ||
* start on a runway, and start the engine manually | * start on a runway, and start the engine manually | ||
* start via autostart (assuming the acft has one) | * start via autostart (assuming the acft has one) | ||
* start in-air: eg use the 'on approach' feature of the launcher | * start in-air: eg use the 'on approach' feature of the launcher (note some aircraft may not work for an in-air start at all) | ||
(note some aircraft may not work for an in-air start at all) | |||
* if the aircraft has terrain variants (eg, skis, floats) and you have time, check they work as expected (eg seaport takeoff and landing for floats). | * if the aircraft has terrain variants (eg, skis, floats) and you have time, check they work as expected (eg seaport takeoff and landing for floats). | ||
| Line 50: | Line 49: | ||
* check altimeter setting (can you set it, can you select inHG vs HPA if the acft supports it) | * check altimeter setting (can you set it, can you select inHG vs HPA if the acft supports it) | ||
* tune NAV1 and check behavior, including from/to flag | * tune NAV1 and check behavior, including from/to flag (might need to be done in air for reception) | ||
* check ground steering (especially if ground tiller mode is supported) | * check ground steering (especially if ground tiller mode is supported) | ||
| Line 63: | Line 61: | ||
** check radar altimeter if fitted (the HUD is good to cross-check this) | ** check radar altimeter if fitted (the HUD is good to cross-check this) | ||
** check stall performance in clean config (is it vaguely plausible, especially) | ** check stall performance in clean config (is it vaguely plausible, especially) | ||
*** clean configuration stall can be checked on the circuit downwind | |||
*** approach configuration stall can be checked on approach, but you might need to go around | |||
** check level flight over-speed performance (time to hit the barber pole at full power). | ** check level flight over-speed performance (time to hit the barber pole at full power). | ||
** check engine performance instruments are somewhat working, keeping in mind most aircraft have very simple fuel/oil/temperature modeling. | ** check engine performance instruments are somewhat working, keeping in mind most aircraft have very simple fuel/oil/temperature modeling. | ||
** check pitch trim works: can you trim for level flight and leave the controls untouched for a few seconds without the aircraft departing straight and level flight? | ** check pitch trim works: can you trim for level flight and leave the controls untouched for a few seconds without the aircraft departing straight and level flight? | ||
| Line 84: | Line 81: | ||
* execute a reset, check nothing breaks :) (the sim might crash...) | * execute a reset, check nothing breaks :) (the sim might crash...) | ||
= Visuals = | == Visuals == | ||
* frame-rate : do you see a large frame-rate drop compared to other aircraft / the UFO. Is it only when in an inside or outside view? | * frame-rate : do you see a large frame-rate drop compared to other aircraft / the UFO. Is it only when in an inside or outside view? | ||
| Line 94: | Line 91: | ||
* does the cockpit use tooltips / knob animations for readability | * does the cockpit use tooltips / knob animations for readability | ||
= Non-standard stuff = | == Non-standard stuff == | ||
This is nice-to-haves, not mandatory | This is nice-to-haves, not mandatory | ||
| Line 105: | Line 102: | ||
* GPWS: if it's fitted, check its callouts on landing are correct | * GPWS: if it's fitted, check its callouts on landing are correct | ||
= Autopilot checks = | == Autopilot checks == | ||
* If the aircraft has an autopilot implemented in the cockpit, check controls work for basic modes (ROLL, PITCH). If the aircraft does not have an autopilot implemented, there is /no/ requirement for the generic autopilot dialog to work successfully, but would be nice to note if it does or doesn't. | * If the aircraft has an autopilot implemented in the cockpit, check controls work for basic modes (ROLL, PITCH). If the aircraft does not have an autopilot implemented, there is /no/ requirement for the generic autopilot dialog to work successfully, but would be nice to note if it does or doesn't. | ||