There is always a big question we get asked and that it is ‘How do you test your software?‘ This is kind of important as ICAO does have guidelines in place, have you seen…

This specifically discusses how to validate your Flight Procedure design software that you may have developed yourself or have purchased as a COTS product.

To test our software we use Unit Testing along with Code Coverage. Our unit testing is divided into two parts, those that our customers would be interested in seeing and using if them want. And, secondly test cases that we develop in-house for our QA and to keep a high percentage for Code Coverage.

Above you can see a view of the Test Explorer in Microsoft Visual Studio, the unit test cases are hierarchical and you can we have included all the examples that are included within ICAO Doc 9906; thankfully the green tick means the tests have passed.

Code Coverage is a percentage value that is the amount of source code that the test cases cover. Hence the higher percentage means that your more of your source code has been tested so if you get to 100% then it means that every bit of the source has been through a test case.

We currently have over 3000 unit test cases which test the software in a variety of target compilations i.e. 32-Bit/64-bit Windows DLL, .NET 8,9,10 DLL’s and the .NET Standard Library 2.0.

These unit tests are part of our build pipeline in Azure DevOps.

If you have any questions or even would like to see our testing then please make contact.