Tuesday Jun 16, 2015

Create Test Logs Like Javadocs

In a new article, Madhu Seelam and Raghunandan Seshadri describe how to build a test framework that ensures logs from test classes and TestNG listeners that are executed in parallel reach the appropriate log file and are organized in a format similar to that of Javadocs.

TestNG is a popular open source test automation framework that provides support for parallel test execution. Java Logging APIs can ensure thread-safe logging from numerous threads and logging within test cases, as well as callback functions within listeners. However, when tests are executed in parallel, the logs from various test cases are interleaved, which makes it difficult to isolate the logs for a given test case.

Using the solution described in this article, all logs from a given TestNG test class reside in one HTML file, and HTML files can be linked into a format similar to that of Javadocs. This enables you to select a package and select the corresponding class to view the logs related to just that test class, even when the tests have been executed in parallel. Read the article

Thursday Sep 22, 2011

Integration Testing for Java EE

A new article by Java Champion Adam Bien, now up on otn/java, titled “Integration Testing for Java EE,” explores the intricacies of integration testing, which is done after a successful execution of unit tests, which however, will often fail. According to Bien, unit tests are fast and fine-grained while integration tests are slow and coarse-grained.

From the article:

“Testing everything inside an embedded container is convenient but unproductive. Java EE 6 components are annotated Plain Old Java Objects (POJOs) and can be easily unit tested and mocked out (see my previous article, “Unit Testing for Java EE.") with Java SE tools such as JUnit, TestNG, or Mockito. Using an embedded container to test your business logic is not only unproductive, but it is also conceptually wrong. Unit tests should validate your business logic, not the container behavior. Also, the majority of integration tests could be easily performed with a local EntityManager (see Listing 1) or a mocked-out container infrastructure. Only a fraction of all integration tests can be beneficially implemented with embeddable containers or test frameworks such as Arquillian.”

Read the complete article here.

About

Insider News from the Java Team at Oracle!

duke
Links


Search

Archives
« July 2015
SunMonTueWedThuFriSat
   
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
 
       
Today