Uploaded image for project: 'Code Tools'
  1. Code Tools
  2. CODETOOLS-6773474

"Clear Result" may produce duplicate items in Tree of Tests.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P2 P2
    • jt4.2
    • None
    • tools
    • b09
    • x86
    • windows_xp
    • Verified

      Javatest 4.2_b05

      1. Start the tool. Open any WD that has some result.
      2. Expand an folder that is full of results.
      3. Select Test1. Right-click/Clear Results.
      4. Result is cleared, test is moved to the last place in this package (6773472).
      5. Now select another test with result. Clear it in the same way.

      It will be moved to the last place in the package - as at the previous step, but it will also REMAIN at its original place, colored with original color. So it will look like test has been duplicated in the package. See attachment.

      If user tries to select that "original" test - it get Error in the console:

      Exception in thread "AWT-EventQueue-0" ** Internal JavaTest Harness error. Please contact the developers. **
      com.sun.javatest.JavaTestError: Error loading result file for Automatic_Readiness/com/sun/readiness/automated/optionalfeatures/bluetooth/ConnectionTests#testProtocolsSupport
      at com.sun.javatest.exec.TP_OutputSubpanel.updateTOC(TP_OutputSubpanel.java:489)
      at com.sun.javatest.exec.TP_OutputSubpanel.updateSubpanel(TP_OutputSubpanel.java:88)
      at com.sun.javatest.exec.TestPanel.updateGUI(TestPanel.java:198)
      at com.sun.javatest.exec.TestPanel.updateGUIWhenVisible(TestPanel.java:137)
      at com.sun.javatest.exec.TestPanel.updatePanel(TestPanel.java:117)
      at com.sun.javatest.exec.TestPanel.setTest(TestPanel.java:95)
      at com.sun.javatest.exec.TestTreePanel.selectTest(TestTreePanel.java:1264)
      at com.sun.javatest.exec.TestTreePanel.access$900(TestTreePanel.java:90)
      at com.sun.javatest.exec.TestTreePanel$Listener.dispatchSelection(TestTreePanel.java:1536)
      at com.sun.javatest.exec.TestTreePanel$Listener.valueChanged(TestTreePanel.java:1475)
      at javax.swing.JTree.fireValueChanged(JTree.java:2823)
      Steps to reproduce on javatest-4_2-fcs-bin-b07-09_dec_2008.zip:
      (exact usecase, i believe it can be reproduced with the sample testsuite as well)

      1. Start JDTS Admin Harness. Open Working directory.
      2. Select Automatic_Readiness/com/sun/readiness/automated/presentedapi
      3. Make sure all tests inside are not ran. (Clear Results, Restart Harness if necessary)
      4. Select all tests.
      5. Run them. Results will appear AND tests will be reordered because of 6782781.
      6. Now select first test in the group. Clear result.

      This will produce duplicated entry in the tree of tests. One test from the bottom will disappear (total number of tests will remain the same).
      See attached 42b07_duplicateTests.jpg.

      Note that behavior is DIFFERENT if user "Clear Results" when tests are in the correct order. It means that reproducing 6782781 is a requirement to reproduce this bug.

      Clicking on the 2nd (duplicated) test causes
      Exception in thread "AWT-EventQueue-0" ** Internal JavaTest Harness error. Please contact the developers. **
      com.sun.javatest.JavaTestError: Error loading result file for Automatic_Readiness/com/sun/readiness/automated/presentedapi/PresentedAPITest#testJSR82_BluetoothOBEX
      at com.sun.javatest.exec.TP_OutputSubpanel.updateTOC(TP_OutputSubpanel.java:489)
      at com.sun.javatest.exec.TP_OutputSubpanel.updateSubpanel(TP_OutputSubpanel.java:88)
      at com.sun.javatest.exec.TestPanel.updateGUI(TestPanel.java:198)
      at com.sun.javatest.exec.TestPanel.updateGUIWhenVisible(TestPanel.java:137)
      at com.sun.javatest.exec.TestPanel.updatePanel(TestPanel.java:117)
      at com.sun.javatest.exec.TestPanel.setTest(TestPanel.java:95)

            bkurotsu Brian Kurotsuchi (Inactive)
            kromanovorcl Konstantin Romanovskiy (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: