Concurrency test effectiveness via mutation testing and dynamic lock elision

A computer program product comprising physical storage media comprising computer executable instructions that when executed by one or more processors cause the one or more processors to perform the following:

• identifying a plurality of synchronization primitives in a section of implementation source code, wherein there is a test suite which is intended to test the section of implementation source code;
• iteratively modifying one or more of the synchronization primitives;
• for each iteration of modifying one or more of the synchronization primitives in the implementation source code, running the test suite to determine if the test suite detects an error caused as a result of modifying the one or more synchronization primitives in the implementation source code;
• determining, for each iteration whether or not the test suite returns an error as a result of modifying one or more synchronization primitives;
• and
• when the test suite does not return an error, providing to a user an indication which indicates at least one of a test adequacy hole for the test suite, an implementation source code fault, or an equivalent mutant of the implementation source code in order to verify the effectiveness of the test suite for detecting concurrency problems and/or product faults within implementation source code.

A computer system comprising one or more processors and one or more computer memory comprising computer executable instructions that when executed by the one or more processors cause the one or more processors to perform the following:

• identifying a plurality of synchronization primitives in a section of implementation source code, wherein there is a test suite which is intended to test the section of implementation source code;
• iteratively modifying one or more of the synchronization primitives by removing or disabling one or more synchronization primitives;
• for each iteration of modifying one or more of the synchronization primitives in the implementation source code, running the test suite to determine if the test suite detects an error caused as a result of modifying the one or more synchronization primitives in the implementation source code;
• determining, for each iteration whether or not the test suite returns an error as a result of modifying one or more synchronization primitives;
• and
• when the test suite does not return an error, providing to a user an indication which indicates at least one of a test adequacy hole for the test suite or an implementation source code fault in order to verify the effectiveness of the test suite for detecting concurrency problems and/or product faults within implementation source code.