One way to achieve this would be to use a custom RunListener, with the caveat that it would be easier to use an annotation rather than javadoc. You would need to have a custom annotation such as:

@TestDoc(text="tests for XXX-342, fixes customer issue blahblah")
@Test
public void testForReallyBigThings() {
    // stuff
}

<代码>RunListener聆听了测试活动,例如测试开始、测试结束、测试失败、测试成功等。

public class RunListener {
    public void testRunStarted(Description description) throws Exception {}
    public void testRunFinished(Result result) throws Exception {}
    public void testStarted(Description description) throws Exception {}
    public void testFinished(Description description) throws Exception {}
    public void testFailure(Failure failure) throws Exception {}
    public void testAssumptionFailure(Failure failure) {}
    public void testIgnored(Description description) throws Exception {}
}

Description载有适用于测试方法的说明清单,因此,采用上述例子,您可采用以下方法获得“通知”测试Doc:

description.getAnnotation(TestDoc.class);

案文照常印发。

然后,你可以使用<代码>RunListener,生成你想要的档案,具体文本是这一检验的结果还是失败,还是被忽略的时间等。 这将是你的习惯报告。

之后,你可以肯定地说出一位习俗听众,使用:

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <version>2.10</version>
  <configuration>
    <properties>
      <property>
        <name>listener</name>
        <value>com.mycompany.MyResultListener,com.mycompany.MyResultListener2</value>
      </property>
  </configuration>
</plugin>

This is from Maven Surefire Plugin, Using JUnit, Using custom listeners and reporters

这种办法的缺点是,就运输回报而言,你没有灵活性,但就格式问题而言,它确实有好处,即文件在一个具体地点,即通知测试。

你们是否看过Maven Sure-fire的报告?

You can generate a HTML report from your JUnit Tests.

http://maven.apache.org/plugins/maven-surefire-report-plugin/

I also know that TestNG ( alternative to JUnit ) has some report generating capabilities. http://testng.org/doc/documentation-main.html#logging-junitreports

I would also recommend log4j http://logging.apache.org/log4j/1.2/manual.html

页: 1 测试报告的良好框架。

I have created a program using testNG and iText which outputs the test results in a nice pdf report. You can put a description of your test in the @Test tag, and that can be included in the .pdf report also. It provides the run times of the tests, and for the entire suite. It is currently being used to test webapps with selenium, but that part could be ignored. It also allows you to run multiple test suites in one run, and if tests fail, it allows you to re-run only those tests without having to re-run the entire suite, and those results will be appended to the original results PDF. See below the image for a link to the source if you are interested. I wouldn t mind this becoming an opensource project as I have a good start on it, though I m not sure how to go about doing that. Here s a screenshot

因此,我说明了如何建立一个关于来源的项目。 这里链接sourceforge链接。

See a good discussion on these tools: What are the differences between BDD frameworks for Java?