Continuous Integration has become a standard development best practice - but it's not always done well. Tests take up much of an application's build time, and poorly constructed test suites can cause long builds, whereupon teams start to circumvent agreed-upon CI practices just get the time to code. InfoQ presents advice and examples in Chapter 6: Continuous Testing from a new CI book.
The release of JUnit 4.4 sees the inclusion of the assertThat method, offering easier reading and new flexibility to the JUnit library.
In this exclusive InfoQ article, Stefan Bodewig explains how to use the XMLUnit Java framework to write tests in the presence of XML.
The QA engineers at Google share their unit testing advice in an ongoing series titled "Testing on the Toilet." The latest installment tackles a common problem: how can the unit tests themselves be refactored without accidentally invalidating the tests?
Alberto Savoia has written a series of four articles describing "characterization testing" - the process of writing unit tests to understand and work with legacy code.
Borland in early October released a beta of Gauntlet continous integration server. Like any continous integration server, Gauntlet automates build and testing but also provides change sandboxing, reporting and trending, failure correlation, replay alongside existing repositories, and easy access to build, test, and run previous project versions.
Andrew Glover has compared TestNG and JUnit 4, taking a look at some features that TestNG has over JUnit 4. Andrew quickly takes the position that TestNG is better for large scale testing, despite JUnit 4's recent addition of annotations and "dramatically relaxed structural rules for test case authoring."
Cedric Beust has announced the launch of TestNG, the popular Testing framework and alternative to JUnit. Alexandru Popescu (TestNG co-founder) is also InfoQ's Chief Architect. TestNG 5 improves configuration, reporting, ease of use, and bug reporting.