Class Summary |
Assert |
Main component for asserting state. You will not instantiate this component directly - the framework makes it available for your TestCases. Use this to see what assertions are available and note that it can easily be extended using the Assert.addDecortor() method or by editing the mxunit-config.xml file, following the examples therein.
|
CSVUtility |
simple utility for creating query from a CSV file. This is meant as a testing utility, not as a bullet-proof component for production code
|
ComponentBlender |
utilities for mixins and other goodness
|
ComponentUtils |
Internal component not generally used outside the framework
|
ConfigManager |
Controlls data retrieved from mxunit-confg.xml
|
DataCompare |
utilities for comparing datatypes (queries, structs)
|
DataproviderHandler |
|
Formatters |
|
HamcrestAssert |
Not Implemented! R/D component testing Hamcrest style assertions to support Descriptive-based test writing.
|
HamcrestMatcher |
Generates Matcher Objects used by the HamcrestAssert component. R/D ... do not use in production
|
HtmlTestResult |
Responsible for generating HTML representation of a TestResult
|
JUnitXMLTestResult |
|
JavaLoader |
Loads External Java Classes, while providing access to ColdFusion classes
|
JavaProxy |
|
MXUnitAssertionExtensions |
Extends core mxunit assertions.
|
MockFactoryFactory |
Fetches mock frameworks for tests. Test writers should not have to deal with this object directly. Use mock(...) instead
|
POIUtility |
Handles the reading and writing of Microsoft Excel files using POI and ColdFusion.
|
PublicProxyMaker |
makes private methods testable
|
QueryTestResult |
Responsible for generating CFQuery representation of a TestResult
|
RemoteFacade |
Main default interface into MXUnit framework from the MXUnit Ecplise Plugin.
|
RemoteFacadeObjectCache |
Mechanism for managing a cache of objects. This is nice to have since the remote facade runs its tests method-at-a-time. Without a cache, you'd incur all the overhead of constructing the Test object(s) multiple times, which is not ideal.
|
Test |
Abstract Class or Interface
|
TestCase |
Composite parent of all TestCases. Extend this class to build and run tests within the MXUnit framework.
|
TestDecorator |
Abstract decorator for extending when you want to have decorators for unit tests
|
TestResult |
Represents the results generated by TestCases. Data is stored as a ColdFusion structure and component has methods for transforming that data to HTML and XML. In General, you will not need to call most methods in this component. The primary ones you will use are: getResults(), getHtmlResults(), getJunitXmlResults(), getXmlResults()
|
TestSuite |
Responsible for creating and running groups of Tests.
|
TestSuiteRunner |
|
TextTestResult |
Responsible for generating plain text representation of a TestResult
|
VersionReader |
utility for reading version information
|
XMLTestResult |
Responsible for generating XML representation of a TestResult
|
XPathAssert |
Assertions for XML and well formed HTML
|
mail |
|