NOTICE: this project requires Java 1.7+ and Maven
Same mechanism could apply for other test framework even other language.
Using log4j for testng logging is quite common, for tests running in parallel in testng, the log outputs to the console will be messed up with each other. This makes failure investigation a little bit harder.
Sure you can specify different logger for different class, or even each per test method, but it doesn't solve the problem when a 3rd-party lib that is logging in its own log4j logger, and most-likely they don't design interface that allow you to pass your test class's "logger" instance for each function call.
Main idea: the logging in each thread is NOT messed up!
So, we can log based on current thread id and merge them together after. To do this, I created a class called GroupedLoggingAppender which extends AppenderSkeleton and implements IReporter: * inside append function(from AppenderSkeleton), write to differnt file for different thread * inside generateReport(from IReporter) function, merge all the files
Have a try:
* Checkout this project then do `mvn clean install`
* you will find 100 lines of output which is messed up on the console as it's from 10 parallel threads
* Then `cat target/output.log.grouped.txt`
* you will see 100 lines with output grouped by thread-id
Detail setup, refer to files in this project:
* set your log4j.properties, add GroupedLoggingAppender
* if you use command line TestNG, use command like this:
java -Doutputdir=. org.testng.TestNG -reporter com.fayaa.logging.GroupedLoggingAppender
* if you use maven-surefire, set listner(yes, not reporter) and system properties similar to pom.xml in this project