Same virtual machine mode for distributed test execution

• US 6,839,647 B2
• Filed: 09/10/2002
• Issued: 01/04/2005
• Est. Priority Date: 09/10/2002
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Volkov, Alexei, Jacobs, Allan S.
• Primary Examiner(s): Shah, Kamini
• Application Number:
  US10/241,091
• Publication Number:
  US 20040049362A1
• Time in Patent Office: 847 Days
• Field of Search: 702/119, 709/203, 700/18, 700/19, 700/20
• US Class Current: 702/119
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

An invention is provided for testing in a Java based environment. The method includes launching a test harness in a first JVM, and starting a virtual machine (VM) agent in a second JVM. The VM agent is placed in communication with the test harness. The VM agent then executes a test application such that both the test application and the VM agent execute in the second JVM. In this manner, the VM agent is restarted using the test harness if the second JVM fails.

Claims

1. A method for performing testing in a Java based environment, comprising the operations of:

launching a test harness in a first Java virtual machine (JVM),

starting a virtual machine (VM) agent in a second JVM, the VM agent being in communication with the test harness;

executing a test application utilizing the VM agent, wherein the test application and the VM agent both execute in the second JVM; and

restarting the VM agent using the test harness if the second JVM fails, and further comprising the operation of passing test data from the test harness to the VM agent, the test data including a subroutine name for a subroutine that executes the test application.

2. A method as recited in claim 1, wherein the test application is executed by calling the subroutine from the VM agent.

3. A method for performing testing in a Java based environment, comprising the operations of:

launching a test harness in a first Java virtual machine (JVM);

starting a virtual machine (VM) agent in a second JVM, the VM agent being in communication with the test harness;

executing a test application utilizing the VM agent, wherein the test application and the VM agent both execute in the second JVM; and

restarting the VM agent using the test harness if the second JVM fails, and further comprising the operation of monitoring the VM agent to detect failure of the VM agent.

4. A method as recited in claim 3, wherein the test harness monitors the VM agent.

5. A method for performing testing in a Java based environment, comprising the operations of:

launching a test harness in a first Java virtual machine (JVM);

starting a virtual machine (VM) agent in a second JVM, the VM agent being in communication with the test harness;

executing a test application utilizing the VM agent, wherein the test application and the VM agent both execute in the second JVM; and

restarting the VM agent using the test harness if the second JVM fails, and wherein a plurality of VM agents are executed, each VM agent being executed in a separate JVM.

6. A method as recited in claim 5, wherein the test harness is in communication with each VM agent of the plurality of VM agents.

7. A method as recited in claim 6, wherein the test harness restarts any VM agent of the plurality of VM agents if the JVM executing the VM agent fails.

8. A system for performing testing in a Java based environment, comprising:

a test harness executed in a first Java virtual machine (JVM); and

a virtual machine (VM) agent executed in a second JVM, the VM agent being in communication with the test harness,

wherein the VM agent is capable of launching test applications in the second JVM based on test data received from the test harness, and wherein the test harness is capable of restarting the VM agent using if the second JVM fails, and wherein the test data includes a subroutine name for a subroutine that executes the test application.

9. A system as recited in claim 8, wherein the VM agent calls the subroutine to execute the test application.

10. A system as recited in claim 9, wherein the test data further includes a class name for the test application.

11. A system as recited in claim 10, wherein the test data further includes arguments associated with the subroutine.

12. A system for performing testing in a Java based environment, comprising:

a test harness executed in a first Java virtual machine (JVM); and

a virtual machine (VM) agent executed in a second JVM, the VM agent being in communication with the test harness,

wherein the VM agent is capable of launching test applications in the second JVM based on test data received from the test harness, and wherein the test harness is capable of restarting the VM agent using if the second JVM fails, and further comprising a plurality of VM agents, each VM agent being executed in a separate JVM.

13. A system as recited in claim 12, wherein the test harness is in communication with each VM agent of the plurality of VM agents, and wherein the test harness restarts any VM agent of the plurality of VM agents if the JVM executing the VM agent fails.

14. A system for performing testing in a distributed Java based environment, comprising:

a test harness executed in a first Java virtual machine (JVM) located on a first computer system;

a harness client executed in a second JVM located on a second computer system, the harness client being in communication with test harness; and

a virtual machine (VM) agent executed in a third JVM on the second computer system, the VM agent being in communication with the harness client,

wherein the harness client facilitates communication between the test harness and the VM agent, and wherein the VM agent is capable of launching test applications in the third JVM based on test data received from the test harness via the harness client, and wherein the test harness is capable of restarting the VM agent using if the third JVM fails.

15. A system as recited in claim 14, wherein the test data includes a subroutine name for a subroutine that executes the test application, and wherein the VM agent calls the subroutine to execute the test application.

16. A system as recited in claim 15, wherein the test data further includes a class name for the test application and arguments associated with the subroutine.

17. A system as recited in claim 14, further comprising a plurality of harness clients, each harness client being in communication with the test harness and an associated VM agent, each VM agent being executed in a separate JVM.

18. A system as recited in claim 17, wherein the test harness is in communication with each VM agent via the associated harness client, and wherein the test harness restarts any VM agent if the JVM executing the VM agent fails.