Clover 2.5 allow developers to execute only the tests that cover code changes. Clover can also prioritize and run failing tests first (test what you need). It’s all about test optimization.
See Clover in action
http://www.atlassian.com/software/clover/videos/test-optimisation-eclipse.jsp
Gerard Meszaros talks about problems and challenges doing unit testing in real-world projects. Starting from a short discussion about the importance of automated unit testing we spend most of this episode to talk about every day problems doing unit testing and how those problems can be solved. Based on this book on xunit testing patterns, Gerard talks about his experiences with unit test smells as an analogy to code smells. He describes an impressive set of unit testing patterns to overcome those difficult testing situations and illustrates them with nice examples everybody doing unit testing will feel familiar with.
listen to the complete podcast interview at sowftware engineering radio, episode 70.
Michael Minella’s JUnit and EasyMock reference card
JUnit and EasyMock are the predominant choices for testing tools in the Java space. This reference card will guide you through the creation of unit tests with JUnit and EasyMock. It contains detailed definitions for unit testing and mock objects as well as a description of the lifecycle of each. The APIs for both JUnit and EasyMock are covered thoroughly so you can utilize these tools to their fullest extent. (more…)
Continuous Integration (CI) facilitates the daily build and test-driven development practices that support high-performance Agile teams. But CI puts significant, and variable, demand on resources. If a team’s compute resources are fixed and demand for those resources increases as the team approaches a release (more tests are being introduced, more code requires build and integration) they can pay a significant penalty in terms of waiting time. (…)
more @ InfoQ: Bamboo Continuous Integration Server Adds Amazon EC2 Build Agents
ABSTRACT
Two key aspects of extreme programming (XP) are unit testing and merciless refactoring. Given the fact that the ideal test code / production code ratio approaches 1:1, it is not surprising that unit tests are being refactored. We found that refactoring test code is different from refactoring production code in two ways: (1) there is a distinct set of bad smells involved, and (2) improving test code involves additional test-specific refactorings. To share our experiences with other XP practitioners, we describe a set of bad smells that indicate trouble in test code, and a collection of test refactorings to remove these smells.
Selenium RC Beta-2 was announced yesterday. It’s possible to download the new Selenium RC Beta-2 version from OpenQA website.
This version is probably the last beta version before the final release expected in few weeks.
*iexplore is now equivalent to *iehta.
*firefox is now equivalent to *chrome.
multi-window mode is the default behaviour.
I’m very excited about the new features (and some bugs solutions!).
In a few days I intend to publish my first impressions using the new Selenium RC Beta-2.
Wanderlei Souza
