Skip to main content
Version: 3.0

External QA Checklist

warning

Completing this checklist is mandatory before launching any new version. There are 2 parts:

1. Code Checklist for Engineers​

To be completed by the Lead Developer or Release Engineer prior to merging into the release branch.

2. Checklist for Real world Beta Testing​

To be completed by QA or Project/Product Managers during Beta testing phase.

Upon Completion: Joint meeting to ensure the QA process is completed before launch.​

Code Checklist for Engineers​

1. Open the Hosting App​

  • Verify performing ‘Start SDK’:
    • Airline is sent properly according to the user-assigned airline.
    • Verify airline is enabled on the SkyPath side.
    • A unique user ID is sent.
  • Verify that a default a/c type is selected:
    • Check the ‘Setup Aircraft’ functionality.

2. Select a Flight, Verify:​

  • Aircraft Type:
    • Is set according to the selected flight on the hosting flight.
    • Defaults to the a/c type if no flight is selected.
  • Route Corridor:
    • The ‘route corridor’ for the selected route is sent.
    • This route corridor should not change during the flight or until the selected flight is changed.
  • ‘Set Flight’ Function:
    • Verify the following details are sent:
      • DEP and DES ICAO codes.
      • Flight number. If the flight number is not available, set an alternative identifier for the flight, e.g., DEP-DES-Airline-Date-Time.
  • END Flight:
    • When a flight is removed, deleted or ended, it is essential to end the flight in the SDK.
    • This is done by calling
    SkyPath.shared.setFlight(nil)
  • Recording Turbulence:
    • Verify that recording turbulence is enabled, even when the layer is off.

3. Start Flight Simulation​

  • Get Data, Verify:
    • A/C category matches the flight.
    • GeoJSON value is not changed during the flight.
    • Verify viewport support if needed.
  • Ensure the SDK is reporting Data, Verify:
    • Reporting works as expected.
    • Reporting is enabled even when the layer is OFF.
    • Verify location access works in the background.

4. Export SkyPath Logs​

  • Ensure application can export technical logs (explained here).
  • Verify technical logs.

5. Check flight data consumption​

  • Check data consumption per flight hour.

Checklist for Real-World Beta Testing​

Share relevant examples of real-world flights using the beta version with the SkyPath Team.

  1. Verify that the app is reporting turbulence data as expected.
  2. Ensure that the SkyPath layer is displayed correctly.
  3. Ensure that data consumption is as expected.
  4. Export SkyPath logs and share them with the SkyPath Team.
  5. Provide SkyPath with users for testing.

When releasing the first version for which the SDK is integrated, also:

  1. Ensure Notifications event is implemented to support QA SkyPath.shared.notifiedTurbulenceSeverity(sev)
  2. Ensure Map Layer event is implemented to support QA SkyPath.shared.setMapLayer(enabled: true)