Testing Airports

Some initial ideas on how to test airports, along with a resultant grade, which can determine whether or not a PR is completed:

Scoring: These questions function as a checklist. The aim should be to bring any releases to tick all boxes. Boxes 1-4 and, ideally, 5 in the "Basic Functionality" section should be checked before pushing. For each airport section there is a basic build-up of functionality. Please consider first completely finishing the main airport before adding secondary airports.

Basic Functionality

1. Does the airport load at all?
2. Does the airport load without any error messages?
3. Is the airport in the correct folder?
4. Does the airport have the correct ICAO code? Does it end with .txt?
5. Is there a properly-named _readme.txt in the same folder?

Main [airport]

1. Does the airport graphically match the provided charts?
2. Do the entry points match with TMA entry points (usually the end point of STARs on charts)?
3. Are there appropriate '[configurations]' blocks?
4. Do the [departure] blocks match the relevant charts?
5. Are the [airlines] airport specific?

If the airport utilizes approach transitions:

1. Do the [approach]/[transition] blocks match the relevant charts?
2. Does [airport1] match provided charts perfectly, as inside the game's limitations?

Secondary [airport]

1. Does the airport graphically match the provided charts?
2. Do the entry points match with TMA entry points (usually the end point of STARs on charts)?
3. Are there appropriate [configurations] blocks?
4. Do the [configurations] not conflict with the main airport?
5. Do the [departure] blocks match the relevant charts?
6. Are the airlines airport specific?

If the airport utilizes approach transitions:

1. Do the '[approach]'/'[transition]' blocks match the relevant charts?
2. Does [airportX] match provided charts perfectly, as inside the game's limitations?