Identifying test gaps using code execution paths

A system comprising:

• a data store comprising an application;
• and
• at least one computing device in communication with the data store, the at least one computing device configured to at least
• identify a plurality of production code paths for the application, each of the plurality of production code paths specifying a respective sequence of code of the application that was executed in a production environment;
• identify a plurality of test code paths for the application, each of the plurality of test code paths specifying a respective sequence of code of the application that was tested in a test environment;
• compare the plurality of production code paths to the plurality of test code paths to identify at least one test gap for the application, the at least one test gap specifying at least one of the plurality of production code paths that is not included in the plurality of test code paths;
• and
• display test gap data specifying the at least one test gap for the application.

A non-transitory computer-readable medium embodying a program that, when executed by at least one computing device, causes the at least one computing device to at least:

• identify a plurality of production code paths for an application, each of the plurality of production code paths specifying a respective sequence of code of the application that was executed in a production environment;
• identify a plurality of test code paths for the application, each of the plurality of test code paths specifying a respective sequence of code of the application that was tested in a test environment;
• compare the plurality of production code paths to the plurality of test code paths to identify at least one test gap for the application, the at least one test gap specifying at least one of the plurality of production code paths that is not included in the plurality of test code paths;
• and
• display test gap data specifying the at least one test gap for the application.