How to Perform Automation Testing of JAVA/J2EE Applications (Part 2)

Broadly, JAVA/J2EE applications are large, incorporating an assortment of components from the front-end interface to the back-end database. For such sizeable applications, automated testing is a more favorable choice than manual testing due to the time savings and reduced effort. Automation testing is typically performed utilizing various tools and frameworks.

A JAVA/J2EE application includes numerous components. Please refer to part 1 of this series titled “Insight into JAVA applications” for additional details.

In summary: JSP denotes the view element or screen, while JSF is a view component framework. Screen validation is carried out through JavaScript. Business logic is facilitated via Servlet, Framework, EJB, Bean, among other JAVA classes.

Automated testing can be carried out using either an individual tool or a mix of different tools for all JAVA components. It is critical to remember that achieving complete automation of application testing may not be possible. The decision to automate hinges on the size and complexity of the application, as well as the preference of developers, testers, and architects. Incorporation of testing considerations during application development yields smoother processes for the team and guarantees the delivery of a high-quality outcome that aligns with customer anticipations.

Stages in Automated Testing Process:

For effective automated testing, comprehensive testing procedure must be contemplated before the application development. The automated testing procedure includes two distinct processes:

1. Crafting the application with the automation testing tool under consideration
2. Carrying out the testing stages

The following flowchart displays the application development procedure incorporating automation testing:

The subsequent stages explain the procedure of automated testing:

#1) Analyze if manual or automated testing should be executed and ascertain which parts of the application should be automated or remain manual.

#2) Upon establishment of the requirement for automated testing, conduct a feasibility analysis.

#3) Based on the known components of the J2EE application and the complexity of the application, select a suitable tool. Depending on the requirement of the test, choose one or more tools.

For instance, for an application based on JSP, a screen navigation instrument like Selenium Webdriver may be adequate. However, for a UI application based on JSF, in addition to JUnit and screen navigation testing tools, specialized JSF tools may be needed for conducting the test.

#4) Analyze and identify the number of testing stages required. For unit, integration, functional/system, and regression testing, choose the appropriate tool for each stage.

#5) Think about the effect of the testing instrument on the design of the application. When automation testing, it is imperative to develop applications keeping the tool in consideration.

#6) Create a pilot or model application, operate the tool, and verify whether the tool provides the anticipated value as projected during the analysis phase. If the tool functions as anticipated, it can be finalized for usage in the application.

#7) Once the application is prepared for testing, draft test scripts and execute them using the selected tool.

Tool Selection

Choosing the appropriate automation testing tool for a J2EE application is mostly contingent on the type of application and the employed technologies. Additionally, numerous other factors play an influencing role in tool selection:

1) Type of application – J2EE applications can be of various types. Some may use frameworks like Struts, Spring, and Hibernate, others may completely rely on server-side technologies like JSP and Servlets, while some applications may encompass the complete development stack, inculding view components, controllers, business logic, and databases.

Based on the enlisted technologies, the selection of tool may fluctuate. For additional details on J2EE component-specific tools, please refer to the upcoming article in this series.

2) Complexity of the application – Testing of complex applications with substantial financial implications for a large user base necessitates detailed testing with suitable tools. On the other hand, simple applications such as those showing data and reports to a limited number of users, can be tested using simple open-source instruments.

3) Type of testing – A tool that is suitable for unit testing may not be perfect for integration testing and vice versa. For instance, JUnit is a common choice for unit testing, while TestNG is frequently used for integration testing.

4) Testing budget – Numerous popular tools are open-source, hence are appropriate for most projects. However, when specific technology-related tools are required, the team needs to evaluate whether the cost of the tool is acceptable.

5) Testing timeframe – Deadlines are a common occurrence in application development. Certain testing tools may need more time for learning, environment setup, and creation of test cases compared to others.

6) Support for environment – Choose J2EE testing tools that are compatible with the target environment of the application. Some tools may only function on certain operating systems or only support specific programming languages.

7) Knowledge of the tester – Testers may have familiarity and experience with certain tools. If the project requirements align with the expertise of the tester, opting for that tool can save time on training and onboarding.

8) Compatibility with other testing frameworks – In large J2EE applications that employ multiple components like JSP, Servlets, JavaScript, JSP, EJB, and databases, one tool alone may not suffice. Therefore, the selected testing frameworks should be able to accommodate other frameworks.

9) Display of test results and statistics – Test readability is of utmost importance in most projects. Hence, it is crucial to present the results of test execution on a properly formatted screen, inclusive of listings of defects, explanations, and other relevant details.

Benefits of Automated Testing in J2EE Applications

• J2EE applications are generally extensive, and manual testing of the entire application can be time-consuming and prone to errors.
• Many J2EE automated testing tools come with in-built features for testing functionality that are specifically designed for the respective components. This significantly simplifies the work for the tester. For example, a JSF testing tool like JSFUnit can test framework classes.
• Automated tests are highly efficient. In manual testing, correctness relies on the skills of the tester.
• Repeated changes in projects and the necessity for repetitive testing of code are effectively managed through automated testing.
• Automated testing allows the execution of a higher number of test cases. As automation is not dependent on human intervention, testing can be carried out at a fast pace, covering a wider range of scenarios within a limited duration.
• Automated testing produces more accurate results in comparison to manual testing as it minimizes dependency on the tester. The testing process also becomes consistent.

Conclusion:

Automation testing is highly recommended for substantial J2EE applications. However, it is important to note that achieving complete automation of application testing might not be attainable. Manual and automated testing complement each other. Though initial tool learning and setup may require time, once the process is set up, testing becomes much more efficient.

In the following article, we will offer a detailed list of popular testing tools and frameworks for J2EE applications, broken down by component.

We welcome your feedback and any questions related to automation testing.