Community
Participate
Working Groups
The testcase might need to be updated. See the results in CVS /org.eclipse.hyades.use.cases/gui_results/Profiling_and_Logging/4.2.2/Platform.UI.LogView.Part2.execution
Marius, would you please attach the testcase steps and step that fails.
It is an automated testcase, please open the execution result to see where it fails.
According to the test results, the following 2 testcases failed. LogSymptomDBCorrelator 1) Imports a log file 2) Creates a symptom database 3) Creates a correlation Verifies by selection that the Log Navigator view is updated. OpeningViewsOnLogViewInputs 1) Open log file using context menu 2) Open log file using tool-bar menu 3) Open log file using the log interaction view 4) Open log file using the thread interaction view 5) Open correlation and ensure it opens with all three views I rerun the testcase manually with TPTP 4.2.2 candidate build and cannot reproduce the problem. Also, when AGR testrun fails, tester is supposed to make sure the test suite is up-to-dated and runs correctly, and open individual defect for each failing testcase instead of a general one for the test suite. Marius, you may want to double check the AGR test and rerun the test again.
Eugene, I've never heard of this rule before, that the tester should fix the testcase, in this case even if I know how to fix it I wouldn't have time. If I remember correctly we decided to enter the test pass with all the testcases in good shape, this seem is not the case. What seems strange to me is that in 4.2.2 although this side of UI didn't change the testcase fails, so how was this working in 4.2 and 4.2.1? I see that the testcase was created and mantained by Ali, please ask him to investigate this problem and fix the testcase if the testcase is the root of the failure. Once the testcase is fixed I'll rerun it.
(In reply to comment #4) > Eugene, I've never heard of this rule before, that the tester should fix the > testcase, in this case even if I know how to fix it I wouldn't have time. > > If I remember correctly we decided to enter the test pass with all the > testcases in good shape, this seem is not the case. > > What seems strange to me is that in 4.2.2 although this side of UI didn't > change the testcase fails, so how was this working in 4.2 and 4.2.1? > > I see that the testcase was created and mantained by Ali, please ask him to > investigate this problem and fix the testcase if the testcase is the root of > the failure. > > Once the testcase is fixed I'll rerun it. > When I said tester, I mean the component owner who used to be the person who run the testpass also, and we changed that kind of assignment in this release. Since Ali is not owner of AGR anymore. I am assigning this to Liz for an investigation.
Created attachment 57351 [details] Execution History for Platform.UI.LogView.Part2 test suite I just ran the Platform.UI.LogView.Part2 test suite for 4.2.2 on my machine and it passed. Please see attached execution history.
Closing as Worksforme.
On my machine it fails every time I run it. We need to investigate why 5 out 16 automated testcases that I run on my machine T60p failed and worked on T40.
Resolving as a duplicate as this is the same description as several other defects. *** This bug has been marked as a duplicate of bug 171623 ***
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
