Community
Participate
Working Groups
Created attachment 198884 [details] Standalone ITE GUI client.log I seem to keep getting constraint violations with Oracle XE on Windows 7 ultimate 64-bit using the Jubula standalone ITE to create a new functional test specification. I have a Swing AUT run from a 64-bit Oracle JDK 1.6.0_26 on the same machine as the ITE. It seems to be related to the difficulty that I sometimes get in object mapping mode. I select the Swing AUT, make sure the green square is around the Swing component that I want to select. I then press CTRL-SHIFT-Q. Most of the time the object mapping view immediately lists the new component. However sometimes it does not. So I press CTRL-SHIFT-Q again on the same component, and then it shows up. However after such an incident, when I edit a test case using this "bad" mapping, I cannot save the test case. Please find attached an edited version of my client.log file.
The initial exception (and source of the problem) seems to deal with optimistic database locking. This would indicate, in your case, that the Component Name with database ID 8008 ("startup_wizard_cancel_button") was modified by some other part of the the software while you were editing the Test Case. I have some questions to help narrow down possible causes of the problem. Any answers you can provide will help us resolve this issue: * Are you working alone in the database? Are you working with a single Jubula client? * Have you performed a Component Name Merge at any point (see "Merging component names" in the User Manual)? * Was the Component Name used in any other Test Cases before the error occurred? * How did you create the Component Name? * Did you map the Component Name while the Test Case Editor that caused the error was open? Or did you first perform the mapping and then open the Test Case Editor?
(In reply to comment #1) > * Are you working alone in the database? Are you working with a single Jubula > client? yes, only me, only the standalone ITE > * Have you performed a Component Name Merge at any point (see "Merging > component names" in the User Manual)? no, not seen the feature yet > * Was the Component Name used in any other Test Cases before the error > occurred? no > * How did you create the Component Name? double click on right-hand side window > * Did you map the Component Name while the Test Case Editor that caused the > error was open? Yes, I thought this was mandatory > Or did you first perform the mapping and then open the Test > Case Editor? No, did not know this could be done
I am able to reproduce the OptimisticLockException in Jubula 1.0, in very specific circumstances. I will attach a Project that fulfills these circumstances. Please let me know if your steps to reproduce are similar. Preconditions: * Project is opened and not missing any reused Projects (i.e. "unbound_modules_concrete" in version 5.0). Steps to reproduce: 1. Start SimpleAdder AUT. 2. Open Object Mapping Editor for SimpleAdder. 3. Open TestCase1 in Test Case Editor. 4. For the Test Case Reference "<ub_cti_replaceText>" Component Names, change the New Name for "nn_nn_cti" from "compWithTextInput" to "nn_nn_cti". 5. Map Component Name "compWithTextInput" to UI Element "value1". 6. Save the Object Mapping Editor. 7. Save the Test Case Editor. 8. Error occurs. Occasionally, I am not able to reproduce the problem the first time, and need to unmap and re-write the New Name before trying again, but the steps seem able to reproduce the problem most of the time. The error does not seem to cause any permanent damage, and the Test Case can be edited again after closing and reopening the Test Case Editor. As stated above, please let me know if this is representative of the problem that you are having.
Created attachment 203061 [details] Project to reproduce the error. (zipped)
yes that sounds about right this has a moderately low occurrence rate, probably once or twice a day
Missed the cutoff for Indigo SR1. Re-scheduling to Indigo SR2.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Since the Genie has reminded us that this hasn't been looked at in a long while. Since I doubt that we're going to get around to looking at it in the near future, I'm marking as wontfix. This doesn't mean it can't be reopened if new information or arguments for fixing it / prioritising it higher come to light. If that's the case, please reopen.
Closed due to comment 8
