com.thoughtworks.qdox.junit
public abstract class APITestCase extends TestCase
Field Summary | |
---|---|
static Comparator | ENTITY_COMPARATOR |
Constructor Summary | |
---|---|
APITestCase() |
Method Summary | |
---|---|
static void | assertApiEquals(URL expected, URL actual)
Compares API of both sources in the readers.
|
static void | assertApiEquals(JavaSource expected, JavaSource actual)
Compares API of both JavaSource objects.
|
static void | assertClassesEqual(JavaClass expected, JavaClass actual)
Compares an actual field to an expected one.
|
static void | assertFieldEquals(JavaField expected, JavaField actual)
Compares an actual field to an expected one.
|
static void | assertFieldsEqual(JavaClass expected, JavaClass actual)
Compares fields from an actual class to an expected one.
|
static void | assertInnerClassesEquals(JavaClass expected, JavaClass actual)
Compares inner classes from an actual class to an expected one.
|
static void | assertInterfacesEqual(JavaClass expected, JavaClass actual)
Compares implemented interfaces from an actual class to an expected one.
|
static void | assertMethodsEqual(JavaClass expected, JavaClass actual)
Compares constructors and methods from an actual class to an expected one.
|
static void | assertModifiersEquals(String msg, AbstractJavaEntity expected, AbstractJavaEntity actual)
Compares modifiers an actual entity.
|
static void | assertNotDir(File expected, File actual) |
protected File | getDir() |
protected File | getRootDir() |
Note: This method is for backward naming compatiblity with xjavadoc.codeunit.CodeTestCase.
Parameters: expected the expected source actual the actual source
Parameters: expected the expected source actual the actual source
As JavaClass doesn't not implements equals
and
hashCode
methods, the comparison is done by hand.
Parameters: expected actual
As JavaField doesn't not implements equals
and
hashCode
methods, the comparison is done by hand.
Parameters: expected actual
The fields are sorted by name before comparison to be sure that even if the fields are defined in a different order, the comparison is still right.
The inner classes are sorted by name before comparison to be sure that even if the inner classes are defined in a different order, the comparison is still right.
The implemented interfaces are sorted by name before comparison to be sure that even if the implemented interfaces are defined in a different order, the comparison is still right.
The constructors and the methods are sorted by name before comparison to be sure that even if the constructors and methods are defined in a different order, the comparison is still right.
The modifiers are sorted by name before comparison to be sure that even if the modifiers are defined in a different order, the comparison is still right.