Community
Participate
Working Groups
Build Identifier: 3.6 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 Reproducible: Always Steps to Reproduce: 1. Create a test case in a test project for swing application 2. After starting AUT record the input of a number which is out of valid interval 3. Add test case to test suite 4. After executing the test suite the error message "Reason: 7009: Test Execution Error." appears.
Hello Oleg, which version of Jubula do you use to perform your test: Jubula Stand-Alone (from http://www.eclipse.org/jubula/download.php), Jubula Plug-In for Eclipse or Eclipse for Testers (EPP)? With best regards Oliver
(In reply to comment #1) > Hello Oleg, > > which version of Jubula do you use to perform your test: Jubula Stand-Alone > (from http://www.eclipse.org/jubula/download.php), Jubula Plug-In for Eclipse > or Eclipse for Testers (EPP)? > With best regards > Oliver Hello Oliver! Thank you for your reply. I use the newest Jubula Stand-Alone, that means, 0.9.0.qualifier. However, I found out that the error does not occur, if I use the keyboard on screen to press enter. A keyboard is located on screen, because the application will be executed by end-users on Touch-Displays without real keyboard. The described error appears only, if I press enter on real keyboard. Oleg
Hi Oleg, If you want to press enter on the real keyboard instead of in the application, you could try using the module ub_app_pressAnyKey_ENTER from the reused project "unbound_modules_concrete" (category: Actions (basic) / Input via Keyboard / Key combination) to perform any key combinations you require in the test. This should allow you to carry on working with the real keyboard while we analyze the problem.
(In reply to comment #3) > Hi Oleg, > > If you want to press enter on the real keyboard instead of in the application, > you could try using the module ub_app_pressAnyKey_ENTER from the reused project > "unbound_modules_concrete" (category: Actions (basic) / Input via Keyboard / > Key combination) to perform any key combinations you require in the test. > > This should allow you to carry on working with the real keyboard while we > analyze the problem. Hello Alex, thank you very much, it worked out! I replaced manually the recorded Key Combination with the action ub_app_pressAnyKey_ENTER from the reused Project "unbound_modules_concrete", and there were no error any more. So you can close this thread. Best wishes, Oleg
closed as requested
