EclipseSource has released the first stable version for an open source JUnit extension that automates testing of REST/HTTP services supporting both synchronous and asynchronous calls.
Cedric Beust has announced TestNG 6.0, with Guice and YAML support and including improvements to the Eclipse TestNG plug-in.
Kent Beck re-released JUnitMax, a continuous test runner plugin for Eclipse that tightens the feedback loop of programmers aiming for a low risk, high throughput pace of development.
JUnit 4.7, which has just reached Release Candidate stage includes a significant new feature: Rules. Rules are, in essence, another extension mechanism for JUnit, which can be used to add functionality to JUnit on a per-test basis. Most examples of custom runners in earlier versions of JUnit can be replaced by Rules, and new capabilities have already been added.
In this presentation recorded at QCon SF 2008, Jeff Brown presents Gallio, a test automation platform, and MbUnit, a test automation framework for .NET. He shows how a test framework works on Gallio and talks about the difficulties faced when building such a platform.
Kent Beck, renowned co-father of XP, TDD, and JUnit itself, tells a story about tracking down a defect in a new JUnit feature, JUnitMax, with unit tests instead of a debugger. He explains a method shown to him by current JUnit lead developer, David Saff, where a high level unit test is recursively inlined until a super concise test is created down at the very root of the defect.
In this interview from QCon London 2008, Erich Gamma discusses the Jazz project, why Eclipse has been successful, the strict Eclipse release schedule, JUnit, Design Patterns, how to identify a design pattern, design patterns and the 'Don't Repeat Yourself' principle, the design pattern community, and whether dependency injection is a design pattern.
JUnit has recently released version 4.5 of the infamous Java testing framework, but is it enough to keep the project in the spotlight? Read more to find what's being talked about regarding the future of JUnit.
A recent article published in IBM developerWorks talks about automating Continuous Integration and Code Inspection tasks in a build process using open source tools. It explains how to install and configure Hudson server with Subversion, Ant, and software inspection tools like FindBugs and PMD to create a build process with continuous feedback on test results and defects.
A new InfoQ article looks at evaluating performance in an iterative and continuous manner.
Code reuse has been the holy grail of software development for a long time. Historically we've tried to achieve code reuse through abstractions and frameworks, which came with their own technical debt. There is now a novel approach that leverages the power of search tools and automated developer tests to search open-source code for matches against interface and behavior.
Spring provides a holistic solution that makes your application's use cases and subsystems easier to test. The emphasis is on testing outside a JEE server or container, thus greatly improving productivity. In this presentation, Spring Creator Rod Johnson discusses integration testing and the support that Spring provides for it.
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.