Community
Participate
Working Groups
To reproduce: 1. Create a Test Suite 2. Add a Test Case e.g. check text 3. Add data and a component name 4. Map the component name to a technical name 5. Add another check text Test Case -> The Test Steps for both are displayed as having incomplete Object Mapping. Mapping the component in the newly added check text Test Case results in both being marked as complete.
This issue should be fixed with the recent major completeness, tooltip, decoration, problems propagation refactoring.
This behavior still occurs following the given instructions. Every test step of the same type is marked with incomplete object mapping if one them is not mapped correctly. After mapping the component and saving the edited TC all the mark disappears on all Test Steps but the Test Suites are still marked with a red cross (error in children), after refreshing the projects this mark disappears too. If you give a component a new name that is not already mapped this behavior does not occur. After adding a new TC of the same type, adding data and saving the Test Suite the Test Cases in this Test Suite are marked with incomplete OM, the TC itself is marked with a warning decorator and the included Test Step is marked with a red cross but the other TCs of the same type in other Test Suites are not marked with missing OM. After refreshing the project the other TCs of the same type in other Test Suites are marked with missing OM again.
I created a TC for this ticket in project CompletenessCheck. We should discuss if this behavior is wrong or right since Jubula marks the Test Steps as the erroneous components. To reproduce this behavior it is important to use the *exact same TCs* (check text and check text) and not to rename the component name of the second added TC. If you use two TCs of the same action (like check text and check focus) this behavior will not occur.
I am increasing the severity of this ticket, as the behaviour also occurs when the un-mapped test case is commented out. This behaviour can be seen in the attached project: In the Test Suite Work_AHA, there is a ub_tbl_replaceTextWithCellSpec module which has no mapping for its nn_nn_tbl component name, and which is commented out. As the project stands, the FULLTESTS are marked as incomplete - within them, it is the modules that deal with tables that are marked as having incomplete object mapping. If the commented-out module is removed, the mapping is marked as correct for the FULLTESTS. The fact that this also occurs with test cases that are commented out means that it is even more confusing for a user - if I can't see the other places where mapping is missing (because the commented-out Test Case is not considered for its own Test Suite), it is very difficult to find the place where the problem is actually occurring.
Created attachment 209607 [details] Project to reproduce the error
Updating attachment with a new example that contains all the projects required to reproduce the behaviour. In the org_eclipse_jubula_qa_caa_rcp_6.0.xml project, the presence of unmapped component names in the WORK_MMue Test Suite leads to the rest of the Test Suites that also use this action also being incomplete. Only deleting the responsible Test Case and then refreshing the project fixes the problem.
Created attachment 212668 [details] Projects to reproduce the error
attachment 212668 [details] is a good example for the problem filed here http://bugzilla.bredex.de/289 but is not related to / caused by test steps of the same action.
I think it just looks like Test Steps of the same action because it's actually always the *exact same* Test Step. Can anyone confirm that so that we have a better idea of what causes the problem?
Closing this bug as a duplicate of: https://bxapps.bredex.de/bugzilla/show_bug.cgi?id=289
