[
http://jira.codehaus.org/browse/QDOX-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed QDOX-169.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.12
Assignee: Robert Scholte (was: Paul Hammant)
> add description of writing proper tests in jira
> -----------------------------------------------
>
> Key: QDOX-169
> URL: http://jira.codehaus.org/browse/QDOX-169
> Project: QDox
> Issue Type: Task
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Fix For: 1.12
>
>
> We get a lot of different ways of test-commits. Sometimes it's a parsing
> failure or some unexpected responses.
>
> The best way to write a test:
> {code}
> public void testDescription() throws Exception {
> JavaDocBuilder builder = new JavaDocBuilder();
> String source = "public class Foo {}";
> //One of next lines
> // builder.addSource(new StringReader(source));
>
> // JavaSource javaSource = builder.addSource(new StringReader(source));
> // JavaClass jClass = javaSource.getClasses()[0];
> }
> {code}
> Would be nice if this was documented somewhere, maybe frontpage of qdox' Jira.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
