Software testing under NetBeans environment

netbeans Software testing under NetBeans environmentAs we’re starting a new development under NetBeans, we have evaluated quite a bit of open source and commercial tools to cover all of our test requirement. This is the first time we undergo a software development under this development platform and we wanted to make sure we pick the right tools for the job. It was a good opportunity for us to go over some of the new tools available. Here are the tools we’re going to use:


We’ll use both tools to cover our lower level UI testing. They will basically be used whenever our UI funtional test tool (QFTest) can’t be used. Jelly will be used as the processing engine while Jemmy will be used to interact with the underlying UI at the Swing/AWT component level.


TestNG will be used to test the Public API of our product, the objects instantiation/destruction, data driven testing, distribution of our tests on slave machine. The whole testNG framework will be integrated within our build framework (based on Husdon and SVN)


XMLUnit will be used for our data injection within our framework and some low level XML validation.


As we’re running tests in parallel with the development of our software, we need to create some mock objects, classes and methods for simulation. We’re using JMockit to create and manage our mocks.


Last but not least, we’re using JUnit with TestNG to manage our overall low-level framework.


This is the only commercial software of our overall test framework. The other tools are used for low level testing. QFTest is primarily used for pure UI functional testing and integration testing. Other choice included Rational Functional tester from IBM but the cost is way higher without much added value.

We’re ran quite a bit of Proof of Concept to end up with this list of tools. We’re confident they will fit the bill. I’ll try to keep you updated on our usage.

 Software testing under NetBeans environment