Unit testing an Enterprise Javabeans (EJB) bean class

• US 8,972,942 B2
• Filed: 07/19/2012
• Issued: 03/03/2015
• Est. Priority Date: 07/19/2012
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Gu, Geng Xian, Li, Hai Dong
• Primary Examiner(s): Zhen, Li B
• Assistant Examiner(s): CHEN, SEN THONG
• Application Number:
  US13/552,870
• Publication Number:
  US 20140026120A1
• Time in Patent Office: 957 Days
• Field of Search: 717/124
• US Class Current: 717/124
• CPC Class Codes: G06F 11/3684 for test design, e.g. generating new test cases
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

An approach for unit testing an Enterprise JavaBeans® (EJB®) bean is presented. A test case for unit testing the EJB® bean is initiated. An indication of a JUnit or an in-container testing mode is received. The unit testing of the EJB® bean in the indicated mode is initiated by injecting the EJB® bean by an injection functionality included in a test framework if the JUnit testing mode is indicated, or by an EJB® container if the in-container testing mode is indicated. A test object in the injected EJB® bean operates business logic on business data by inserting, updating or deleting business data, or by selecting business data to send to a client, thereby generating a set of resulting business data. An assertion operation on the set of resulting business data against expected data determines whether the test case succeeds or fails.

Claims

1. A method of unit testing an enterprise javabeans (EJB) bean, the method comprising the steps of:

a computer initiating a test case for a unit testing of the EJB bean with test data, the step of initiating the test case including a step of the computer receiving an indication that indicates a JUnit testing mode, which is a technique of unit testing any EJB bean by employing JUnit testing in a unit testing framework for Java programming language;

the computer determining the indication does not indicate an in-container testing mode, which is a technique of unit testing any EJB bean on an EJB container of a Websphere application server by employing annotation and runtime injection provided by EJB architecture;

based on the received indication indicating the JUnit testing mode and not indicating the in-container testing mode, the computer initiating the unit testing of the EJB bean by performing the unit testing of the EJB bean in the JUnit testing mode, but not in the in-container testing mode, by injecting the EJB bean at runtime by creating an instance of a Plain Old Java Object (POJO) of the EJB bean, which employs an injection functionality provided by a CommonTestCase class that integrates a base class of the in-container testing mode and a base class of the JUnit testing mode, and the CommonTestCase class being an extension of a TestCase class of the JUnit testing mode;

a test object in the injected EJB bean operating business logic on business data by performing a step of inserting the business data into a database, updating the business data in the database, deleting the business data from the database, or selecting the business data to send to a client, an outcome of the step of operating the business logic being a set of resulting business data;

the computer retrieving expected data corresponding to the test data and subsequently, the computer asserting the set of resulting business data against the retrieved expected data;

based on the step of asserting the set of resulting business data against the retrieved expected data, the computer determining the test case is executed successfully in the JUnit testing mode;

based on the test case being executed successfully, the computer determining a status of the test object changing from unstable to stable; and

based on the status of the test object changing from unstable to stable, the computer receiving a second indication that indicates the in-container testing mode but not the JUnit testing mode, and in response, the computer continuing the unit testing of the EJB bean by performing the unit testing of the EJB bean in the in-container testing mode by (1) re-using the test case without a change to the test case, the test case having been employed in the unit testing of the EJB bean in the JUnit testing mode and (2) the EJB container injecting the EJB bean directly by the injection functionality provided by the CommonTestCase class.

2. The method of claim 1, further comprising the steps of:

subsequent to the step of injecting the EJB bean by the EJB container, the test object in the EJB bean operating the business logic on the business data by performing another step of inserting the business data into the database, updating the business data in the database, deleting the business data from the database, or selecting the business data to send to the client, an outcome of the step of operating the business logic subsequent to the step of injecting the EJB bean by the EJB container being a second set of resulting business data;

the computer asserting the second set of resulting business data against the expected data; and

based on the step of asserting the second set of resulting business data against the expected data, the computer determining the test case succeeds or fails.

3. The method of claim 1, wherein the step of performing the unit testing of the EJB bean in the in-container testing mode by re-using the test case implements functionality of a ServletTestSuite wrapper provided by an Apache Cactus unit testing framework.

4. The method of claim 1, further comprising the step of:

the computer determining a status of a source code of the test object is unstable, wherein the step of receiving the indication that indicates the JUnit testing mode but not the in-container testing mode is based on the status of the source code being unstable.

5. The method of claim 1, wherein the step of initiating the unit testing of the EJB bean is performed in an environment provided by the Websphere application server without requiring a reboot or a redeployment of the Websphere application server.

6. The method of claim 1, further comprising the step of the computer automatically performing the unit testing of the EJB bean from a beginning of a preparation of the test data to an end of an assertion of the set of resulting business data, without requiring a manual preparation of the test data.

16. The method of claim 1, further comprising:

providing at least one support service for at least one of creating, integrating, hosting, maintaining, and deploying computer-readable program code in the computer, the program code being executed by a processor of the computer to implement the steps of initiating the test case, determining the indication does not indicate the in-container testing mode, initiating the unit testing, operating the business logic, retrieving the expected data, asserting, determining the test case is executed successfully, determining the status of the test object, receiving the second indication, continuing the unit testing.

7. A computer system comprising:

a central processing unit (CPU);

a memory coupled to the CPU;

a computer-readable storage device that is not a signal and that is coupled to the CPU, the storage device containing instructions that are carried out by the CPU via the memory to implement a method of unit testing an enterprise javabeans (EJB) bean, the method comprising the steps of;

the computer system initiating a test case for a unit testing of the EJB bean with test data, the step of initiating the test case including a step of the computer system receiving an indication that indicates a JUnit testing mode, which is a technique of unit testing any EJB bean by employing JUnit testing in a unit testing framework for Java programming language;

the computer determining the indication does not indicate an in-container testing mode, which is a technique of unit testing any EJB bean on an EJB container of a Websphere application server by employing annotation and runtime injection provided by EJB architecture;

based on the received indication indicating the JUnit testing mode and not indicating an in-container testing mode, the computer system initiating the unit testing of the EJB bean by performing the unit testing of the EJB bean in the JUnit testing mode, but not in the in-container testing mode, by injecting the EJB bean at runtime by creating an instance of a Plain Old Java Object (POJO) of the EJB bean, which employs an injection functionality provided by a CommonTestCase class that integrates a base class of the in-container testing mode and a base class of the JUnit testing mode, and the CommonTestCase class being an extension of a TestCase class of the JUnit testing mode;

a test object in the injected EJB bean operating business logic on business data by performing a step of inserting the business data into a database, updating the business data in the database, deleting the business data from the database, or selecting the business data to send to a client, an outcome of the step of operating the business logic being a set of resulting business data;

the computer system retrieving expected data corresponding to the test data and subsequently, the computer system asserting the set of resulting business data against the retrieved expected data; and

based on the step of asserting the set of resulting business data against the retrieved expected data, the computer system determining the test case is executed successfully in the JUnit testing mode;

based on the test case being executed successfully, the computer system determining a status of the test object changing from unstable to stable; and

based on the status of the test object changing from unstable to stable, the computer system receiving a second indication that indicates the in-container testing mode but not the JUnit testing mode, and in response, the computer system continuing the unit testing of the EJB bean by performing the unit testing of the EJB bean in the in-container testing mode by (1) re-using the test case without a change to the test case, the test case having been employed in the unit testing of the EJB bean in the JUnit testing mode and (2) the EJB container injecting the EJB bean directly by the injection functionality provided by the CommonTestCase class.

8. The computer system of claim 7, wherein the method further comprises the steps of:

subsequent to the step of injecting the EJB bean by the EJB container, the test object in the EJB bean operating the business logic on the business data by performing another step of inserting the business data into the database, updating the business data in the database, deleting the business data from the database, or selecting the business data to send to the client, an outcome of the step of operating the business logic subsequent to the step of injecting the EJB bean by the EJB container being a second set of resulting business data;

the computer system asserting the second set of resulting business data against the expected data; and

based on the step of asserting the second set of resulting business data against the expected data, the computer system determining the test case succeeds or fails.

9. The computer system of claim 7, wherein the step of performing the nit testing of the EJB bean in the in-container testing mode by re-using the test case implements functionality of a ServletTestSuite wrapper provided by an Apache Cactus unit testing framework.

10. The computer system of claim 7, wherein the method further comprises the step of:

the computer system determining a status of a source code of the test object is unstable, wherein the step of receiving the indication that indicates the JUnit testing mode but not the in-container testing mode is based on the status of the source code being unstable.

11. The computer system of claim 7, wherein the step of initiating the unit testing of the EJB bean is performed in an environment provided by the Websphere application server without requiring a reboot or a redeployment of the Websphere application server.

12. The computer system of claim 7, wherein the method further comprises the step of the computer system automatically performing the unit testing of the EJB bean from a beginning of a preparation of the test data to an end of an assertion of the set of resulting business data, without requiring a manual preparation of the test data.

13. A computer program product, comprising:

a computer-readable storage device that is not a signal; and

a computer-readable program code stored in the computer-readable storage device, the computer-readable program code containing instructions that are carried out by a central processing unit (CPU) of a computer system to implement a method of unit testing an enterprise javabeans (EJB) bean, the method comprising the steps of;

the computer system initiating a test case for a unit testing of the EJB bean with test data, the step of initiating the test case including a step of the computer system receiving an indication that indicates a JUnit testing mode, which is a technique of unit testing any EJB bean by employing JUnit testing in a unit testing framework for Java programming language;

the computer system determining the indication does not indicate an in-container testing mode, which is a technique of unit testing any EJB bean on an EJB container of a Websphere application server by employing annotation and runtime injection provided by EJB architecture;

based on the received indication indicating the JUnit testing mode and not indicating an in-container testing mode, the computer system initiating the unit testing of the EJB bean by performing the unit testing of the EJB bean in the JUnit testing mode, but not in the in-container testing mode, by injecting the EJB bean at runtime by creating an instance of a Plain Old Java Object (POJO) of the EJB bean, which employs an injection functionality provided by a CommonTestCase class that integrates a base class of the in-container testing mode and a base class of the JUnit testing mode, and the CommonTestCase class being an extension of a TestCase class of the JUnit testing mode;

a test object in the injected EJB bean operating business logic on business data by performing a step of inserting the business data into a database, updating the business data in the database, deleting the business data from the database, or selecting the business data to send to a client, an outcome of the step of operating the business logic being a set of resulting business data;

the computer system retrieving expected data corresponding to the test data and subsequently, the computer system asserting the set of resulting business data against the retrieved expected data; and

based on the step of asserting the set of resulting business data against the retrieved expected data, the computer system determining the test case is executed successfully in the JUnit testing mode;

based on the test case being executed successfully, the computer system determining a status of the test object changing from unstable to stable; and

based on the status of the test object changing from unstable to stable, the computer system receiving a second indication that indicates the in-container testing mode but not the JUnit testing mode, and in response, the computer system continuing the unit testing of the EJB bean by performing the unit testing of the EJB bean in the in-container testing mode by (1) re-using the test case without a change to the test case, the test case having been employed in the unit testing of the EJB bean in the JUnit testing mode and (2) the EJB container injecting the EJB bean directly by the injection functionality provided by the CommonTestCase class.

14. The program product of claim 13, wherein the method further comprises the steps of:

subsequent to the step of injecting the EJB bean by the EJB container, the test object in the EJB bean operating the business logic on the business data by performing another step of inserting the business data into the database, updating the business data in the database, deleting the business data from the database, or selecting the business data to send to the client, an outcome of the step of operating the business logic subsequent to the step of injecting the EJB bean by the EJB container being a second set of resulting business data;

the computer system asserting the second set of resulting business data against the expected data; and

based on the step of asserting the second set of resulting business data against the expected data, the computer system determining the test case succeeds or fails.

15. The program product of claim 13, wherein the step of performing the unit testing of the EJB bean in the in-container testing mode by re-using the test case implements functionality of a ServletTestSuite wrapper provided by an Apache Cactus unit testing framework.

17. The computer program product of claim 13, wherein the method further comprises the step of:

the computer system determining a status of a source code of the test object is unstable, wherein the step of receiving the indication that indicates the JUnit testing mode but not the in-container testing mode is based on the status of the source code being unstable.

18. The computer program product of claim 13, wherein the step of initiating the unit testing of the EJB bean is performed in an environment provided by the Websphere application server without requiring a reboot or a redeployment of the Websphere application server.

19. The computer program product of claim 13, wherein the method further comprises the step of the computer system automatically performing the unit testing of the EJB bean from a beginning of a preparation of the test data to an end of an assertion of the set of resulting business data, without requiring a manual preparation of the test data.