Shulou(Shulou.com)06/02 Report--

Today, I will show you what the testing process of J2EE application is like. The content of the article is good. Now I would like to share it with you. Friends who feel in need can understand it. I hope it will be helpful to you. Let's read it along with the editor's ideas.

J2EE is an architecture that uses the java2 platform to simplify complex issues related to the development, deployment and management of enterprise solutions. J2EE technology is based on the standard version of the java2 platform. J2EE not only consolidates many of the advantages of the standard edition, but also provides full support for EJB,Servlet,JSP,XML. J2EE includes four layers: customer layer, web layer, business layer and enterprise information system layer. A multi-tier distributed application model means that it is divided into components according to functional application logic, and these different components that make up J2EE applications can be installed on the same server or on different servers. J2EE has a complex structure and many levels, and the requirements will be constantly updated, so how to ensure the quality of the final development becomes very important.

Two types of tests are defined in the idea of extreme programming. 1. Unit test, the test of the internal module of the system. In order to adapt to the J2EE platform, integration testing closely integrated with the J2EE container has also been developed. two。 Functional testing. Another thing that is often heard in software testing is performance testing. Because performance testing is closely related to the needs of customers, it is classified as an extended application of acceptance testing. Considering the structure and technology of J2EE, it is necessary to test not only the technology used in it, but also the relationship between the layers.

The following is a specific introduction to the testing process of J2EE applications, including the test types and testing tools used in each stage of testing.

Unit is the foundation of the whole software engineering, so the quality of the unit is the foundation of the whole software quality. In J2EE development, the minimum testable units are encapsulated classes or objects, and JUnit is a good unit testing tool. The core category of Junit is Testcase, where each testcase represents a command object, and Testcase contains several test methods. Used to test whether the output of the member method in the category under test is the same as the expected result. Another core category of the Junit platform is testSuite, where each testSuite represents a composite object, and a testSuite can consist of multiple Testcase or multiple testSuite.

On the basis of unit testing, all modules need to be assembled into a system according to the requirements. The issues to be considered in the development process are as follows

1. Whether the function of one module has an adverse impact on the function of another module.

two。 Whether the combination of each sub-function can achieve the expected parent function.

Therefore, integration testing can be carried out at the same time of unit testing to find and eliminate problems that may occur in module connections. Integration testing provides an environment for the J2EE container to quickly and easily verify whether the interaction between domain objects and the J2EE container is logical. Therefore, the object of the integration test is an EJB,Servlet or JSP program code as the basic unit. Cactus is a tool born to solve the problem of integration testing. Cactus is an extension of Junit, but it is somewhat different from Junit in that it is divided into three different test categories: Jsp Testcase,Servlet testcase,filter testcase. The test code of Junit is only on the client side, while the test code of cactus has two parts: server and client, which work together.

Functional testing examines the code at the common API boundary with the goal of verifying the behavior described in the use case and testing whether the system meets the required functionality. Every time a periodic functional test is completed, it also represents the completion of part of the system function.

HttpUnit is a testing tool developed for functional testing. HttpUnit is a virtual browser written in java to simulate the internal behavior of the browser. The HttpUnit platform simulates the request object sent by users browsing the website, sends it to the destination website, and other websites send the response object back to httpUnit. HttpUnit is a black-box testing tool, so just focus on how to write test code that simulates browser behavior.

It is important that the function is executed correctly, but what is the effect of multi-user execution at the same time? This requires performance testing. In J2EE application testing, the main thing to do is stress testing. Most stress tests verify that the application can respond to a large number of user requests in a short period of time. The JMeter testing tool can automatically send set requests and track the response time of the application. By analyzing the test report, we can find the bottleneck of the J2EE application and optimize the application.

The above is the whole content of the testing process of J2EE application, and you can search the previous article or browse the following article to learn more about the testing process of J2EE application. I believe the editor will add more knowledge to you. I hope you can support it!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.