| Summary: | Performance problem during checking menu bar items | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] Jubula | Reporter: | Felix Ziesel <Felix.Ziesel> | ||||
| Component: | UI | Assignee: | Markus Tiede <markus.tiede> | ||||
| Status: | CLOSED FIXED | QA Contact: | Oliver Goetz <Oliver.Goetz> | ||||
| Severity: | critical | ||||||
| Priority: | P2 | CC: | Achim.Loerke, alexandra.schladebeck, zeb.ford-reitz | ||||
| Version: | 1.0.0 | ||||||
| Target Milestone: | Juno M6 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
It is possible to reproduce this bug using the CI of the EPP for the Testing package. Linux is very fast (about 150 seconds). Windows needs 20 minutes. http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=d531e5ed83e2eb40c472adea641ff0a5f3346767 may have fixed this. Can you test this again with a Jubula version that contains that changeset? Please check whether this issue has been fixed by ZF's changeset. I was not able to reproduce this behavior after the changeset using a VM with Win7. I´m closing this ticket as fixed. |
Created attachment 195948 [details] Projects and screenshots PRECONDITION: 1. You need the appended project. 2. Open Testing Package project 3. Ensure that you have access to a virtual machine containing the Testing Package 1. Start FULLTEST If everything went fine the tests will finish in 3 or 4 minutes. In some cases the check of the menu bar entries seems to need too long (look in the appended snapshots). The test cases that are done are: 1. Check for menu bar existence (no problems here) 2. Check for entry existence (if an Action Error occur here the action will be retried with 500 millisec timeout) 3. Check for entry enablement (if an Action Error occur here the action will be retried with 500 millisec timeout) The check in 2 and 3 can take a very long time. (more than 10 seconds each) The AUT shows no behaviour during that time.