JUnit-addons, version 1.4
API specification
JUnit-addons is a collection of helper classes for JUnit.
See:
Description
Packages |
junitx.ant |
Provides classes that integrate some of JUnit-addons functionalities for the
Ant build tool. |
junitx.extensions |
Provides classes that are meant to extend the framework. |
junitx.framework |
Provides classes that extend the junit framework. |
junitx.tool |
Provides classes that are meant to be used externally to the framework or the test classes. |
junitx.util |
Provides classes that can be used by the test classes for enhance functionalities. |
JUnit-addons is a collection of helper classes for JUnit.
The best way to contribute to the project is to write your own additional classes. Use them for
some time and if you see that you can't live without them, then submit your code into the project's
patch section.
You can either submit a patch (cvs diff -u > mypatch.patch) or simply your source files.
Alternatively you can request for a feature but you'll have to wait until someone decides to implement
it.
I hope you'll find this project useful,
- Vladimir R. Bossicard (vbossica@users.sourceforge.net)
Main features
- PropertyManager: if your tests need external properties (e.g.
username/password) this is the best way to organize them.
(more)
- TestSetup: like in a TestCase the tearDown method should
(IMO) always be invoked
(more)
- assertEquals for strings: offers an alternative to the 'expected <......>
but was <... ...>'
(more)
- ResourceManager: when the tests have to access resources that are
time-consuming to create this class is a real saver. You loose the strict
independance of the tests, but it's not difficult to live with it
(more)
- PrivateAccessor: I never had to use this class but it's interesting to see
how the accessibility of a field can be dynamically modified
(more)
In the pipeline
The different modules can be checked out from CVS. All code is alpha and no support is
provided. If it works for you, fine; if it doesn't, you're out of luck.
- new assert classes (ListAssert, JndiAssert, DOMAssert) as other utilities are placed in the
sandbox module before being added into the main module.
- some PMD rules to check the validity of JUnit tests. (module 'junit-addons-pmd')
- yet another runner, but this time with custom listeners, services and an easily embeddable
test runner engine. It's like apricot, but for JUnit only. (module 'junit-addons-runner')
JUnit-addons resources
Articles about JUnit-addons
Contributors
- Dean Chalker: FileAssert class
- Benoit Xhenseval
- Paul Holser
- Greg Vaughn
- Naidu Purushotham: *SuiteBuilder classes
- Dan Griffin: bug reports
Copyright © 2002-2003 Vladimir R. Bossicard. All Rights Reserved.