The IzPack revamp comes with more tests which have been used for the refactoring.
Introduction
New code have been written with unit tests and integration tests has been made to check the overall sanity of the application.
The integration test execute a compilation of an IzPack installer, load the generated jar in the classpath and execute the installer. When the installer frame appear, a swing robot interact with the interface to realize the installation.
This system allows to launch almost real installation and check live result automatically on several platform.
Tests tools
We use several testing tools
- fest as the swing robot for interface interactions
- TestNG in the izpack-test module which provides interesting features for integration tests like dependent test method.
- Hamcrest to realise assertions with assertThat(). See hamcrest tutorial for more details. It is quite powerful thanks to its matcher system.
- And Junit , no need to present it.
Running Tests
Maven execution
Tests are automatically run by maven during the build. Just run "mvn install" to run tests on the project.
IDE execution
You can run tests directly in your IDE.
If you use Eclipse, you need to install the TestNG eclipse plugin to run tests in the test-module.
Headless execution
It is possible to run graphical tests on a headless environment using Xvfb. Given that you have xvfb installed, you simply need to run
Maven build using xvfbxvfb-run -s "-screen 0 1280x1024x24" $MAVEN_BIN/mvn clean installYou can also run headless tests from your IDE by starting a Xvfb server and specifying the DISPLAY variable to the DISPLAY created by the xvfb server.
Skip graphical tests
If you don't have Xvfb or don't want to run graphical tests, you can use the bamboo profile with maven (use -Pbamboo).
This profile run a special testNG suite excluding all tests using graphical elements.