Automated tracking of consistent software test failures

One or more computing devices, comprising:

• one or more processors;
• and
• memory storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
• receiving a set of evidence of test (EOT) files associated with testing of a software application using a plurality of tests, wherein:
• the software application is repeatedly tested over a period of time by executing the plurality of tests at different times in association with different test execution instances during the period of time, and
• different EOT files, of the set of EOT files, indicate corresponding results of the plurality of tests that are associated with the different test execution instances over the period of time;
• identifying consistently-failing tests, in the plurality of tests, by determining that the set of EOT files indicates that the consistently-failing tests failed consistently during all of the different test execution instances throughout the period of time;
• generating a failed test list that identifies the consistently-failing tests indicated by the set of EOT files;
• retrieving a task list from a software development management platform, wherein the task list indicates active tasks associated with identified consistently-failing tests in the plurality of tests;
• opening one or more new tasks, in the software development management platform, that correspond to one or more individual consistently-failing tests indicated in the failed test list that are not associated with the active tasks indicated by the task list, wherein the one or more new tasks are assignable to one or more developers in the software development management platform;
• identifying a set of existing tasks, indicated by the task list, that correspond with one or more tests that:
• were previously determined to be consistently failing, and
• are not identified by the failed test list;
• determining, based on the one or more tests not being identified by the failed test list, that the one or more tests associated with the set of existing tasks are no longer consistently failing;
• and
• closing the set of existing tasks in the software development management platform based on determining that the one or more tests are no longer consistently failing.

One or more non-transitory computer-readable media storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:

• receive a set of evidence of test (EOT) files associated with testing of a software application using a plurality of tests, wherein:
• the software application is repeatedly tested over a period of time by executing the plurality of tests at different times in association with different test execution instances during the period of time, and
• different EOT files, of the set of EOT files, indicate corresponding results of the plurality of tests that are associated with the different test execution instances over the period of time;
• identifying consistently-failing tests, in the plurality of tests, by determining that the set of EOT files indicates that the consistently-failing tests failed consistently during all of the different test execution instances throughout the period of time;
• generating a failed test list that identifies the consistently-failing tests indicated by the set of EOT files;
• retrieving a task list from a software development management platform, wherein the task list indicates active tasks associated with identified consistently-failing tests in the plurality of tests;
• opening one or more new tasks, in the software development management platform, that correspond to one or more individual consistently-failing tests indicated in the failed test list that are not associated with the active tasks indicated by the task list, wherein the one or more new tasks are assignable to one or more developers in the software development management platform;
• identifying a set of existing tasks, indicated by the task list, that correspond with one or more tests that:
• were previously determined to be consistently failing, and
• are not identified by the failed test list;
• determining, based on the one or more tests not being identified by the failed test list, that the one or more tests associated with the set of existing tasks are no longer consistently failing;
• and
• closing the set of existing tasks in the software development management platform, based on determining that the one or more tests are no longer consistently failing.