Community
Participate
Working Groups
Component names propagated from within Event Handlers (using the checkbox in the component names view) are not available for editing when the test case containing the Event Handler is reused. To reproduce: 1. Create an empty Test Case called TC1 2. Add an action that requires a component name (e.g. check text) to TC1 as an Event Handler (any error type and reentry type). 3. Activate the checkbox in the component names view. 4. Save the Test Case TC1. 5. Create a new Test Case called TC2 and reuse TC1 in it. The expected behavior is that the propagated component name is visible and editable in the component names view for the reused TC1 in TC2. I have checked this in the current build, and in versions 4.3, 4.2 and 3.2, and this expected behavior wasn't present in either of them. The category "Example 1" in the attached project shows this scenario. However, it seems that the component name for the Event Handler Test Case can be "indirectly" propagated: 1. Create a test case called TC3 2. Add the action "check selection by index" for combo box to TC3 as a normal Test Case. 3. Enter a new name for the nn_nn_cbx component name in the component names view (e.g. combobox) and select the checkbox to propagate it. 4. Save the Test Case TC3. 5. Add the action "select by index" for combo box to TC3 as an Event Handler, (e.g. as a check failed with retry as the reentry type). 6. In the component names view, activate the checkbox to propagate the old name nn_nn_cbx. 7. Save the Test Case TC3. 8. Create a new Test Case called TC4 and reuse TC3 in it. 9. Add TC4 to a Test Suite, complete the data and perform the object mapping. The Test Suite is marked as incomplete. Looking in the object mapping editor shows that the component "nn_nn_cbx" is not mapped. Selecting "show corresponding specification" provides "TC4/TC3" as the place where the component name comes from. This example is shown in the category and Test Suite "Example 2" in the attached project.
Created attachment 188212 [details] Project with example test cases
The workaround for this issue is described (more clearly) and exemplified in issue https://bxapps.bredex.de/bugzilla/show_bug.cgi?id=39
As discussed with the product owner, this is actually a missing feature and should be more highly prioritized.
Crosslink: This has also been noted in the GUIdancer Bugzilla: https://bxapps.bredex.de/bugzilla/show_bug.cgi?id=217
i have this problem, but the links with the workarounds are not functioning anymore.
The fixed links are: https://bugzilla.bredex.de/show_bug.cgi?id=39 https://bugzilla.bredex.de/show_bug.cgi?id=217
I think this issue is caused by the CompNamesBP.getAllCompNamesPair method using the getNodeListIterator method of the INodePO's - as usual, Event Handlers are ignored by this method. The solution is to use the new getAllNodeIter iterator from this (not yet merged) contribution: https://git.eclipse.org/r/#/c/81526/ See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=500825
New Gerrit change created: https://git.eclipse.org/r/82926
This problem also affected the Search Replace action.
see Comment 8
Gerrit change https://git.eclipse.org/r/82926 was merged to [master]. Commit: http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=e760e59d331b231158ee4bc19f3537c259440427
closing as merged to master