Object mappings accross AUTs/configurations [message #1066849] |
Thu, 04 July 2013 18:39 |
Guy Perron Messages: 8 Registered: July 2013 |
Junior Member |
|
|
Hello,
I am using Jubula 7.1 to drive tests on different Eclipse versions which run different versions of the same plugins as rcp.
If I design the test on say Kepler, it plays back the test fine.
The problem occurs when I use a different configuration, which drives Eclipse 3.8.2 (could be a different one).
The test stops with Component Not found Error. That specific component I defined to be called NewReviewGroup and mapped to a technical name which is identical between the 2 configurations.
But somehow, Jubula doesn`t see them as being the same.
How can I workaround this without having to redo the mapping for every configuration ?
The intention is to run the same tests when new eclipse and/or plugins are released. With this current problem, I don`t see how that can be.
Thanks
[Updated on: Fri, 05 July 2013 14:57] Report message to a moderator
|
|
|
Re: Object mappings accross AUTs/configurations [message #1067128 is a reply to message #1066849] |
Sat, 06 July 2013 07:41 |
|
Unfortunately there are technical reason for a different default OM between RCP 3.x and 4.x AUTs. We thought about solving this by adding some sort of heuristic but gave up because it would fail less often, but if it fails you'll never guess what happened.
You will get a rock solid OM if you put names on your components by calling setData("TEST_COMP_NAME", "your unique ID for the component") This is detailed in the Jubula documentation.
- Achim
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.40557 seconds