Injecting faults into program for testing software

• US 8,752,027 B2
• Filed: 09/14/2011
• Issued: 06/10/2014
• Est. Priority Date: 09/14/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Noureddine, Sadek A., Yegorov, Artem
• Primary Examiner(s): Khatri, Anil
• Application Number:
  US13/231,958
• Publication Number:
  US 20130067439A1
• Time in Patent Office: 1,000 Days
• Field of Search: 717124-132
• US Class Current: 717/130
• CPC Class Codes: G06F 11/3624 by performing operations on the source code, e.g. via a compiler
• CPC Class Codes: G06F 11/3672 Test management
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

Aspects of the subject matter described herein relate to injecting faults into programs for testing. In aspects, a program is instrumented with instrumentation points. A request that an exception be raised at an instrumentation point is received. In response, a sink is configured to listen for the event associated with the instrumentation point. The sink is further configured to cause the exception to be raised to the program in response to receiving the event. The exception may be raised without modifying code of the program.

Claims

1. A method implemented at least in part by a computing device having a processor, the method comprising:

with the processor,

monitoring for a notification of an event from a program during execution, the program being configured to generate the notification at a target execution point of the program;

in response to the monitored notification of the event, causing an exception to be raised at the target execution point in the program without the program being under conditions that would otherwise cause the exception to be raised in the program and without modifying code of the program, the exception indicating to the program that an action of the program is not executed normally;

obtaining data regarding how the program responds to the raised exception; and

allowing determination of whether the program correctly handles the exception based on the obtained data.

2. The method of claim 1 wherein causing the exception to be raised includes causing at least one of a file operation failure or a memory allocation failure to be raised at the target execution point.

3. The method of claim 1 wherein the event includes one of a entry into a routine, exiting from a routine, setting a variable value, establishing a connection, or terminating a connection.

4. The method of claim 1 wherein raising the exception to the program includes raising the exception to the program without modifying binary, byte, or source code of the program.

5. The method of claim 1 wherein raising the exception to the program includes raising the exception and at least one other exception to the program in response to the monitored notification of the event.

6. The method of claim 1 wherein raising the exception to the program includes raising the exception in parallel with executing a line of code of the program associated with the target execution point, after the line of code but before any other lines of code are executed, or at a target time after the line of code is executed.

7. The method of claim 1, further comprising, in response to the monitored notification of the event, transmitting a message to the program, the message indicating to the program that the notification of the event is processed.

8. A computer storage medium excluding propagating signals per se, the computer storage medium containing instructions, that when executed by a computing processor, causing the computing processor to perform a process comprising:

receiving a definition of a sink for testing a program, the sink being configured to;

monitor for a notification of an event from a program during execution, the program being configured to generate the notification at a target execution point of the program; and

in response to the monitored notification of the event, cause an exception to be raised at the target execution point in the program without the program

being under conditions that would otherwise cause the exception to be raised in the program and without modifying code of the program, the exception indicating to the program that an action of the program is not executed normally;

collecting data regarding how the program responds to the raised exception; and

presenting the collected data to a program tester to determine if the program correctly handles the raised exception.

9. The computer storage medium of claim 8 wherein the event is a first event, and wherein receiving the definition of the sink includes receiving a definition of the sink that is also configured to monitor for a notification of a second event from the program during execution, the second event being different from the first event.

10. The computer storage medium of claim 8 wherein:

the raised exception is a first exception;

receiving the definition of the sink includes receiving the definition of the sink that is also configured to, in response to the monitored notification of the event, cause a second exception to be raised in the program without the program being under conditions that would otherwise cause the second exception to be raised in the program; and

the second exception is different from the first exception.

11. The computer storage medium of claim 8 wherein receiving the definition of the sink includes receiving the definition of the sink that is configured to, in response to the monitored notification of the event, cause a plurality of additional exceptions to be raised in the program without the program being under conditions that would otherwise cause the plurality of additional exceptions to be raised in the program.

12. The computer storage medium of claim 8 wherein receiving the definition of the sink includes receiving the definition of the sink that is configured to, in response to the monitored notification of the event, cause a plurality of additional exceptions to be raised in the program without the program being under conditions that would otherwise cause the plurality of additional exceptions to be raised in the program, the additional exceptions being raised at the target execution point in the program.

13. The computer storage medium of claim 8 wherein receiving the definition of the sink includes receiving the definition of the sink that is configured to, in response to the monitored notification of the event, cause the exception to the program to be raised in parallel with executing a line of code of the program associated with the target execution point, after the line of code but before any other lines of code are executed, or at a target time after the line of code is executed.

14. The computer storage medium of claim 8 wherein receiving the definition of the sink includes receiving the definition of the sink that is configured to, in response to the monitored notification of the event, transmit a message to the program, the message indicating to the program that the notification of the event is processed.

15. A computing system, comprising:

a computing processor; and

a memory operatively coupled to the computing processor, the memory containing instructions, that when executed by the computing processor, cause the computing processor to perform operations comprising;

performing execution of a program having an executing point corresponding to a line of code in the program, the program being configured to generate a notification when the execution of the program reaches the execution point;

monitoring for and detecting the generated notification from the program during execution;

in response to the detected notification from the program, injecting an exception into the execution of the program at the target execution point without the program being under conditions that would otherwise cause the exception and without modifying the code of the program, the exception indicating to the program that an action of the program is not executed normally;

collecting data regarding how the program responds to the injected exception; and

presenting the collected data to a program tester to determine if the program correctly handles the injected exception.

16. The computing system of claim 15 wherein injecting the exception includes injecting at least one of a file operation failure or a memory allocation failure at the execution point.

17. The computing system of claim 15 wherein the line of code of the program corresponds to one of a entry into a routine, exiting from a routine, setting a variable value, establishing a connection, or terminating a connection.

18. The computing system of claim 15 wherein:

the injected exception is a first exception;

injecting the exception includes injecting a second exception into the execution of the program without the program being under conditions that would otherwise cause the second exception to be raised in the program; and

the second exception is different from the first exception.

19. The computing system of claim 15 wherein injecting the exception includes injecting the exception in parallel with executing a line of code of the program associated with the target execution point, after the line of code but before any other lines of code are executed, or at a target time after the line of code is executed.

20. The computing system of claim 15 wherein the operations further include transmitting a message to the program, the message indicating to the program that the notification is processed.