| "Default Event Handler" is triggered instead of my customized handler [message #904493] |
Tue, 28 August 2012 10:28  |
 Peter S.
Messages: 6
Registered: August 2012 |
Junior Member |
|
|
Hi. I'm using Jubula v1.2.1 on an RCP-application, reading testdata from Excel-files.
My testcases have subtestcases and there are multiple nested checkStringValue-checks with "check failed"-handlers, mainly to ensure that only data of the current subtestcase is considered.
Those handlers worked fine and grew in number, but now there is always one teststep in my testsuite, that does not trigger my handler and immediately performs the reentry. Because of those missing steps, shortly afterwards my testrun is stopped due to an action error. Test results show, that the default event handler has been performed, despite there are customized event handlers everywhere.
If I'm varying the order of my testdata, the default event handler is often triggered on another position (few steps later or earlier).
Why could my handlers be ignored? How can it be, that the testcase I chose for the handler is not performed, but if I change the reentry type from CONTINUE to BREAK it does the break?
Thanks in advance, Peter
[Updated on: Tue, 28 August 2012 10:29] Report message to a moderator |
|
|
] 
Search
Help
Register
Login
Home
