| Running Jubula on a windows Jenkins agent requires a display plugin? [message #1142870] |
Thu, 17 October 2013 18:40  |
Eclipse User |
|
|
|
Hi all,
I have set up Jubula to run on a windows Jenkins agent. If I build the Jubula test job on Jenkins with a remote desktop connection opened to the windows Jenkins agent (a virtual machine), it would build fine. But if I close the remote desktop connection and try to build the Jubula test job, it would fail to perform any test step on GUI widget. How should I fix this?
The following is a snippet of the console output:
C:\Program Files\jubula_7.1.00055\jubula>testexec.exe -c "C:\Program Files (x86)\Jenkins\workspace\JUDB_Jubula_tests\com.teradata.judb.jubula.tests\judb_feature_launcher.xml"
Thu Oct 17 15:34:59 PDT 2013 Using configuration file:
C:\Program Files (x86)\Jenkins\workspace\JUDB_Jubula_tests\com.teradata.judb.jubula.tests\judb_feature_launcher.xml
Thu Oct 17 15:35:01 PDT 2013 AUT Agent: Connecting to "localhost:60000" ...
Thu Oct 17 15:35:03 PDT 2013 AUT Agent: connection established.
Thu Oct 17 15:35:03 PDT 2013 Database: Connecting as "sa" to "jdbc:h2:~/.jubula/database/embedded;MVCC=TRUE;AUTO_SERVER=TRUE;DB_CLOSE_ON_EXIT=FALSE"...
Thu Oct 17 15:35:07 PDT 2013 Database: Connection established.
Thu Oct 17 15:35:07 PDT 2013 Database: Loading project "judb_feature" in version "1.0"...
Thu Oct 17 15:35:08 PDT 2013 Database: Project loading completed.
Thu Oct 17 15:35:08 PDT 2013 Project: Checking completeness
Thu Oct 17 15:35:08 PDT 2013 Checking completeness of Test Suite "Launch_debug"...
Thu Oct 17 15:35:08 PDT 2013 AUT: Starting AUT: AUT FEATURE
Thu Oct 17 15:35:45 PDT 2013 Start Test Suite: Launch_debug
Thu Oct 17 15:35:45 PDT 2013 Executing Test Suite "Launch_debug"...
Thu Oct 17 15:35:45 PDT 2013 Preparing execution of Test Suite "Launch_debug"...
Thu Oct 17 15:35:45 PDT 2013 AUT: Connecting to "aut feature"...
Thu Oct 17 15:35:57 PDT 2013 AUT: Connection established.
Thu Oct 17 15:35:58 PDT 2013 Resolving predefined Variables
Thu Oct 17 15:35:58 PDT 2013 Resolving Test Steps to execute...
Thu Oct 17 15:35:59 PDT 2013 Activating AUT...
Thu Oct 17 15:35:59 PDT 2013 Test Suite "Launch_debug" execution...
Thu Oct 17 15:35:59 PDT 2013 Test Case: debug_button_launchConfig
Thu Oct 17 15:35:59 PDT 2013 Step: Select Menu Entry by Textpath on DebugDropDownAction
Thu Oct 17 15:36:16 PDT 2013 Event Handler: Default Event Handler
Thu Oct 17 15:36:16 PDT 2013 Step: Wait for Window
Thu Oct 17 15:36:32 PDT 2013 Event Handler: Default Event Handler
Thu Oct 17 15:36:32 PDT 2013 Step: Replace Text on Text Component
Thu Oct 17 15:36:34 PDT 2013 Event Handler: Default Event Handler
Thu Oct 17 15:36:34 PDT 2013 Step: Select Node by Textpath on Tree
Thu Oct 17 15:36:35 PDT 2013 Event Handler: Default Event Handler
Thu Oct 17 15:36:35 PDT 2013 Step: Key Combination
Thu Oct 17 15:36:37 PDT 2013 Event Handler: Default Event Handler
Thu Oct 17 15:36:37 PDT 2013 Step: Expand Node by Textpath on Tree
Thu Oct 17 15:36:38 PDT 2013 Event Handler: Default Event Handler
Thu Oct 17 15:36:38 PDT 2013 Step: Click on Button Component ("Debug")
Thu Oct 17 15:36:39 PDT 2013 Event Handler: Default Event Handler
Thu Oct 17 15:36:39 PDT 2013 Step: Wait for Window to Close
Thu Oct 17 15:36:40 PDT 2013 Test Case: judb_uninstallation
Thu Oct 17 15:36:40 PDT 2013 Step: Select Menu Entry by Textpath on Menu Bar
Thu Oct 17 15:36:53 PDT 2013 Event Handler: Default Event Handler
Thu Oct 17 15:36:53 PDT 2013 Step: Wait for Window
Thu Oct 17 15:37:09 PDT 2013 Event Handler: Default Event Handler
Thu Oct 17 15:37:09 PDT 2013 Step: Click on Button Component ("Installation Details")
Thu Oct 17 15:37:10 PDT 2013 Event Handler: Default Event Handler
Thu Oct 17 15:37:10 PDT 2013 Step: Wait for Window
Thu Oct 17 15:37:26 PDT 2013 Event Handler: Default Event Handler
Thu Oct 17 15:37:26 PDT 2013 Step: Select Entry by Textpath (Specify Column) on Tree
Thu Oct 17 15:37:27 PDT 2013 Event Handler: Default Event Handler
Thu Oct 17 15:37:27 PDT 2013 Step: Click on Button Component ("Uninstall...")
Thu Oct 17 15:37:28 PDT 2013 Event Handler: Default Event Handler
Thu Oct 17 15:37:28 PDT 2013 Step: Wait for Window to Close
Thu Oct 17 15:37:29 PDT 2013 Step: Wait for Window to Close
Thu Oct 17 15:37:30 PDT 2013 Step: Wait for Window
Thu Oct 17 15:37:45 PDT 2013 Event Handler: Default Event Handler
Thu Oct 17 15:37:45 PDT 2013 Step: Wait for Window to Close
Thu Oct 17 15:37:46 PDT 2013 Step: Click on dialog.button.finish ("Finish")
Thu Oct 17 15:37:47 PDT 2013 Event Handler: Default Event Handler
Thu Oct 17 15:37:47 PDT 2013 Step: Wait for Window to Close
Thu Oct 17 15:37:48 PDT 2013 Step: wait_for_loading
Thu Oct 17 15:37:58 PDT 2013 End of Test Suite
As you can see, it ends up with hitting the default event handler for all GUI test steps.
Any idea would be greatly appreciated. Thanks a lot
|
|
|
|
|
|
| Re: Running Jubula on a windows Jenkins agent requires a display plugin? [message #1149576 is a reply to message #1144202] |
Tue, 22 October 2013 02:59  |
| Eclipse User |
|
|
|
Here is what we are doing (we are using Hudson, Jenkins should be reasonable similar):
The test machine does an auto login (this is possible for Windows, Linux and OSX, no idea for other systems).
As part of the login process (this is very system dependent) it downloads the Hudson slave jar and connects to the Hudson master as a slave node. This ensures that the Hudson slave has a display to run the GUI tests.
The Hudson jobs starts the necessary Jubula agents (minimum is autagent, we also run the testexec on the slaves) on the test slave.
This has been working for us for several years now.
- Achim
|
|
|
Powered by
FUDForum. Page generated in 0.03588 seconds
Home