SYSTEM AND METHOD FOR TESTING A SOFTWARE ENGINE

• US 20090164847A1
• Filed: 12/19/2007
• Published: 06/25/2009
• Est. Priority Date: 12/19/2007
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Data Services Incorporated (Verizon Communications Inc.)
• Inventors: Sawhney, Yogesh, Kumar, Balaji, Miller, Anne L.
• Granted Patent: US 8,689,053 B2
• Time in Patent Office: Days
• US Class Current: 714/38
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

A software engine has a base system in communication with service subsystems and test subsystems. The base system, the service subsystems, and the test subsystems are software applications that exchange data with one another while operating within the software engine. In one exemplary mode of operation, the base system receives outputs from the service subsystems. In another exemplary mode of operation, the base system receives outputs from the test subsystems that simulate the outputs generated by the service subsystems. An exemplary method of testing the software engine is also provided. Specifically, the illustrative method includes receiving an output during a service mode, switching from the service mode to a testing mode, and receiving the simulated output during the testing mode. The method steps may be performed by a computer executing instructions stored on a computer-readable medium.

Claims

1. A software engine comprising:

a base system having at least both a service mode and a testing mode;

at least one service subsystem in communication with said base system during said service mode; and

at least one test subsystem in communication with said base system during said testing mode and wherein said at least one test subsystem is configured to simulate an output from said at least one service subsystem during said testing mode.

2. A software engine as set forth in claim 1, wherein said base system is configured to receive an output from said at least one service subsystem during said service mode and an output from said at least one test subsystem during said testing mode.

3. A software engine as set forth in claim 1, further comprising a user interface in communication with said base system and said at least one test subsystem.

4. A software engine as set forth in claim 3, wherein said user interface is configured to switch said base system between said service mode and said testing mode.

5. A software engine as set forth in claim 1, wherein said base system is in communication with at least one of said service subsystem and said test subsystem via a network.

6. A software engine as set forth in claim 1, wherein said base system, said at least one service subsystem, and said at least one test subsystem include software applications stored in a computer-readable medium.

7. A software engine as set forth in claim 6, wherein said software applications are configured to be executed by at least one computer.

8. A software engine as set forth in claim 1, wherein at least one of said service subsystems is in communication with another of said service subsystems.

9. A software engine as set forth in claim 1, wherein at least one of said test subsystems is in communication with another of said test subsystems in said testing mode.

10. A software engine as set forth in claim 1, wherein at least one of said test subsystems is in communication with at least one of said service subsystems in said testing mode.

11. A method comprising:

establishing communication between a base system and at least one service subsystem;

receiving at least one output from the service subsystem during a service mode;

establishing communication between the base system and at least one test subsystem during a testing mode; and

receiving at least one simulated output from the at least one test subsystem.

12. A method as set forth in claim 11, further including severing communication between the base system and the at least one service subsystem.

13. A method as set forth in claim 11, further including severing communication between the base system and the at least one test subsystem.

14. A method as set forth in claim 11, wherein receiving at least one output from the at least one service subsystem includes receiving at least one output at from the at least one service subsystem at the base system.

15. A method as set forth in claim 11, wherein receiving at least one simulated output from the at least one test subsystem includes receiving at least one simulated output from the at least one test subsystem at the base system.

16. A method as set forth in claim 11, wherein receiving at least one simulated output from the at least one test subsystem is simultaneous with receiving at least one output from the at least one service subsystem.

17. A method as set forth in claim 16, wherein receiving at least one simulated output from the at least one test subsystem is sequential to receiving at least one output from the at least one service subsystem.

18. A method as set forth in claim 11, wherein receiving at least one simulated output from the at least one test subsystem includes configuring the test subsystem to simulate at least one output from the at least one service subsystem.

19. A method as set forth in claim 11, wherein the base system, the at least one service subsystem, and the at least one test subsystem are software applications.

20. A method as set forth in claim 11, wherein said method is performed by a computer executing instructions stored in a computer-readable medium.