Siebel IP17: Siebel Test Automation Running With Only 1 Launch Test Step Issue java -jar C:\Siebel
(Doc ID 2330931.1)
Last updated on OCTOBER 27, 2022
Applies to:
Siebel CRM - Version 17.0 [IP2017] to 20.4 [Release V17]Information in this document applies to any platform.
Symptoms
On Siebel IP 2017
When trying to execute a Test Script that contains only 1 Test Step that is Launch , the Jenkins worker does not trigger any remote session to open Siebel Application.
The Jenkins Job output show:
Starting Siebel Test Automation Execution...
java -jar C:\Siebel\DISA\DesktopIntSiebelAgent\plugins\SiebelTestAutomation\Framework\SiebelTestAutomation.jar C:\Siebel\DISA\DesktopIntSiebelAgent\plugins\SiebelTestAutomation
STE2.17.8DISA
File already exists.
Exit Value: 0
INFO :: Siebel Test Automation Execution Completed Successfully.
INFO :: Uploading Attachments...
The issue can be reproduced at will with the following steps:
1. Create a Test Script with ONLY one step, Launch
2. Create a Automation Execution Configuration to execute this single Test Script
3. Run the Job in Jenkins, the worker never launches the Siebel Application
4. In the Jenkins console output we see:
Starting Siebel Test Automation Execution...
java -jar C:\Siebel\DISA\DesktopIntSiebelAgent\plugins\SiebelTestAutomation\Framework\SiebelTestAutomation.jar C:\Siebel\DISA\DesktopIntSiebelAgent\plugins\SiebelTestAutomation
STE2.17.8DISA
File already exists.
Exit Value: 0
INFO :: Siebel Test Automation Execution Completed Successfully.
INFO :: Uploading Attachments...
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |