Bugzilla – Full Text Bug Listing
| Summary: | resolve "No Component Type exists!" error!? | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] Jubula | Reporter: | Tobias Eiss <Tobias.Eiss> | ||||
| Component: | UI | Assignee: | Project Inbox <jubula.ui-inbox> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Oliver Goetz <Oliver.Goetz> | ||||
| Severity: | critical | ||||||
| Priority: | P3 | CC: | alexandra.schladebeck | ||||
| Version: | 2.0 | Keywords: | triaged | ||||
| Target Milestone: | Kepler SR1 | ||||||
| Hardware: | PC | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
This situation occurs when: - a component name that has been propagated and then renamed at the place of reuse is no longer accessible, either because the name with which the component was propagated is changed or the propagation is removed (i.e. the checkbox is deactivated). The message disappears once the Test Case has been saved. The information can be used to transfer the previous "new name" as a new "new name" in the case of a rename. It is documented [1], but the documentation was not very clear, and hard to find. I've moved the section up a level, so that it is less hidden, and also adapted it [2]. In terms of a quick fix, the steps to : - save the Test Case and therefore remove the message with no action, or - perform a transfer to a newly propagated name could be possible, although I'm not sure how the second option would look. I wonder whether the problem here is more the difficulty understanding the message. The steps to resolve the problem are not difficult, but it is a complex use case. Would more easily available information about the situation be enough? [1] http://help.eclipse.org/kepler/topic/org.eclipse.jubula.client.ua.help/html/manual/node157.html [2] http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=20a6804b7bd04a5db6dc2efe55f558084acbe7e8 @Triaged:? Having spoken to Tobi, I can add the information that the error apparently occurred after having *renamed* a component name in the component names browser. This action has no effect on the hierarchy, and should not lead to this problem. However, I am not able to reproduce the problem, and neither is Tobi. Since the problem is currently not reproducible, I'm closing this as worksforme. That doesn't mean that the ticket shouldn't be reopened if Tobi or anyone else rediscovers this problem. |
Created attachment 233619 [details] No Component Type exists! Jubula shows an error decoration in the Test Suite Browser. When I navigate to this error, I can see in the Component Names View in column "Type" a "No Component Type exists!" error. I do not know exactly what actions I took to reach this error state, and I have no idea how to resolve this problem. I would expect Jubula to offer possible solutions to resolve this problem (Quick Fix or similar).