Eclipse Community Forums: Jubula » Reason: 7009: Test Execution Error

Help

Home

Home » Archived » Jubula » Reason: 7009: Test Execution Error(Component name can not be resolved)

Show: Today's Messages :: Show Polls :: Message Navigator

Reason: 7009: Test Execution Error [message #683851]

Tue, 14 June 2011 14:08

Oleg Kusnetsov

Messages: 7
Registered: June 2011
Location: Braunschweig

Junior Member

Hello !

In ITE of Jubula I've created a test case in a Test project for swing
application. Before creating the test case I've started the AUT. In AUT I've
recorded the input of a number which is out of valid interval. In the AUT, the
error message appeared.

Then, in ITE I stopped recording for test case. The recording has created three
Test steps:
1) Replace Text
2) Key Combination
3) Replace Text

In AUT I clicked in the error message window on "OK"-Button.

In the next step, I added the TestCase to the TestSuite. When I execute the
Test Suite I got the following error message:

>An error occured.

Reason: 7009: Test Execution Error.

The component name "71e59396845045438412bea1072a1ecf" in Test Case
"MainBladeSpeed" in Test Step "Key Combination" can not be resolved.
Please make sure that all of your reused Projects are currently available in
the database and not marked as missing in the Test Case Browser.<

What are the steps to solve this problem?

Best wishes,
Oleg

Attachment: error_message.JPG
(Size: 23.13KB, Downloaded 874 times)
Attachment: test_result.JPG
(Size: 7.74KB, Downloaded 672 times)

Report message to a moderator

Re: Reason: 7009: Test Execution Error [message #683860 is a reply to message #683851]

Tue, 14 June 2011 14:39

Oliver Goetz

Messages: 219
Registered: May 2011

Senior Member

Hello Oleg,

thank you for your entry. I already answered your Jubula Bugzilla entry (https: //bugs.eclipse.org/bugs/show_bug.cgi?id=349315). You can track all changes made to your issue in the Bugzilla
With best regards
Oliver

Report message to a moderator

Re: Reason: 7009: Test Execution Error [message #684393 is a reply to message #683860]

Wed, 15 June 2011 14:25

Oleg Kusnetsov

Messages: 7
Registered: June 2011
Location: Braunschweig

Junior Member

Hello,

the problem reported was solved. The recorded Key Combination should be replaced by the action ub_app_pressAnyKey_ENTER which is located in unbound_modules_concrete. Then, during the execution of the test suite (which contains the above mentioned test case) the error does not occur any more.

best wishes,
Oleg

Report message to a moderator

Previous Topic:	(no subject)
Next Topic:	Automate Jubula Test Runs with Jenkins

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 19:15:32 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter