Regardless of your political beliefs, as an agile and test-infected developer, we'd like you to consider the benefits of adhering to strict, some might say "dictatorial", limits on the way that you write your unit tests as well as the code being tested (SUT).
We should clarify , right up front, that these restrictions apply only to unit tests (and not system tests or integration tests, which are also of great importance to the success of any project). However, your unit tests, at least one for each class in your codebase, should be clean , and decoupled from one another, and . Your unit test suite should run ultra-fast, so that you're encouraged to run it often. We think you should be able to run thousands of unit tests and get your green bar in a few seconds. Achieving that kind of performance takes major discipline on the part of the developer, and Ashcroft helps you learn that discipline by failing tests which stray from acknowledge best practices.
Remember, the most severe restrictions often lead to the most creative solutions.
Ashcroft has an implementation of the Java seurity manager. Once registered (See FAQ), it will start monitoring the process. Ashcroft can be configured through additional VM parameter (See Ashcroft Configuration).
You can download the attached jar at this page.
Or you can build it from the Subversion repository: svn://beaver.codehaus.org/ashcroft/scm
Open issues and bugs
Copyright 2004-2005 (C) Obie Fernandez and Aslak Hellesoy. All Rights Reserved.