> What you guys think about a XML outputer for both Sun's API
> and ours and check for their equality? I believe it'll be useful for
> other cases too, we can use the xml equality code for testing
> ejb-jar.xml and other xmls for example.
>
If it can be used as a more general test bench for XDoclet - yes.
Otherwise, the outogenerated JUnit classes is better IMHO. See below.
> > One other idea I have is to write a javadoc doclet which scans a big
> > source
> > tree and generates JUnit test classes (using xdoclet's
> > template engine.) This is a good way to test if xjavadoc works the
> same
> > way
> > as javadoc. This shouldn't be too hard to do, and it
> > would make us really sure that xjavadoc is ready for action.
>
> "generates JUnit test classes"? I don't get it.
>
-A javadoc doclet that does this in its start(RootDoc)
for all classes in test hierarchy
tagshandler.setClass(...)
invoke template engine
-And a XClassTest.j which extracts all imaginable data from the current
class and generates JUnit code - just like it would generate a
RemoteInterface for that matter...
public class <XDtXjavadocTest:testClass/> extends TestCase {
private XClass _testedClass;
public void setUp() {
_testedClass = XJavaDoc.getInstance().getXClass
(<XDtXjavadocTest:testedClass/>);
}
<XDtXJavadocTest:forAllInerfaces>
public void testImplements<XDtXJavadocTest:interface/> {
assert( "<XDtXJavadocTest:testedClass/> should implement
<XDtXJavadocTest:interface>", _testedClass.implementsInterface
(<XDtXJavadocTest:interface/>);
}
</XDtXJavadocTest:forAllInerfaces>
}
Aslak.
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
