During my last project, I was given a task to choose one of the best tools for performance testing among open source tools available in market. After evaluation and little research I came up with JMeter.
For many years now, I have always found myself going back to TestNG whenever it comes to doing Unit Testing with Java Code. Everytime, I picked up TestNG, people have asked me why do I go over to TestNG especially with JUnit is provided by the default development environment like Eclipse or Maven.
I came across today a case where I needed to complete a unit-integration test of some quite complex enterprise Java code. Actually it was JSF backing bean with a specific inheritance chain, wired all together with some EJB's.
Arlo Belshee posed a question by email last week: "What are the characteristics of a good test suite?" Interesting question. He plans to collate the answers on his blog sometime soon. Meanwhile, here's my answer:
This is an, let's call it accidental post. I was looking into transactional CDI observers and playing around with GlassFish embedded to run some integration tests against it. But surprisingly this did not work too well and I am still figuring out, where exactly the problems are while using the plain embedded GlassFish for that.
It’s easy to collect unit test code coverage because all of the common tools are geared up for it. This article will explain how you can add unit test coverage to your Maven application in 10 minutes. We will use the excellent Jacoco code coverage library to show how easy it is.
A common thing I come across is that teams using a mocking framework assume they are mocking. They are not aware that Mocks are just one of a number of 'Test Doubles' which Gerard Meszaros has categorised at xunitpatterns.com.