You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Eddie O'Neil (JIRA)" <be...@incubator.apache.org> on 2005/02/21 19:23:48 UTC

[jira] Resolved: (BEEHIVE-156) testRecorderCore.xml 'playback.tests' target deletes junit tests result data after create html report

     [ http://issues.apache.org/jira/browse/BEEHIVE-156?page=history ]
     
Eddie O'Neil resolved BEEHIVE-156:
----------------------------------

     Assign To: Scott Symmank  (was: Eddie O'Neil)
    Resolution: Won't Fix

After looking at this, it seems that what's happening is that the test recorder produces two virtually identical JUnit result files in:

  build/testRecorder/junit/<suitename>

as:

  TEST-org.apache.beehive.netui.tools.testrecorder.client.MasterTestRecorderJUnitTest.xml
  TESTS-TestSuites.xml

The former file is deleted, but the latter is left in place (because the delete pattern is TEST-*).  Seems like the right thing to do is use the one that's still there.  

The real trick will be figuring out why there are two files showing up since we should only be producing one.  Scott, I'd use the latter file for your reporting needs. s

> testRecorderCore.xml 'playback.tests' target deletes junit tests result data after create html report
> -----------------------------------------------------------------------------------------------------
>
>          Key: BEEHIVE-156
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-156
>      Project: Beehive
>         Type: Bug
>   Components: NetUI
>  Environment: All
>     Reporter: Scott Symmank
>     Assignee: Scott Symmank
>     Priority: Minor
>  Attachments: patchfile.txt, testRecorderCore-PATCHED.xml, testRecorderCoreDIFF.htm
>
> The 'playback.tests' target in testRecorderCore.xml generates 
> a junit report after running its tests. After generating the 
> the junit html/xml reports, it deletes the test result data
> (TEST-*.xml).
> This step should not be necessary, and inhibits aggregating
> results of successive test runs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira