Running Test Scripts in Batch Mode via the Command Line using runReference does not Pick Up the Correct Test Run Record
(Doc ID 3073534.1)
Last updated on FEBRUARY 24, 2025
Applies to:
Siebel CRM - Version 22.12 and laterInformation in this document applies to any platform.
Symptoms
Running test scripts in batch mode via the command line (without Jenkins) does not select the correct test run;instead, it chooses the oldest test run. This behavior is observed from the command line output .
C:\DISA\jre\bin>java -jar C:\DISA\DesktopIntSiebelAgent\plugins\SiebelTestAutomation\Framework\KWDPresetup.jar /d C:\DISA /j <USERID> /g <PASSWORD> /r <SIEBEL AI URL> /c <EAI COMP> /n <
INFO :: Checking config.properties file to fetch HTTP Proxy Details...
INFO :: No HTTP Proxy Details found. Process will continue...
INFO :: Total no of parallel executions opted by User is - 1
INFO :: Attempt - 1 to fetch the RUN-ID
INFO :: Making REST Call To Siebel Server To Fetch RUN-ID....
INFO :: REST GET URL :: https://xxxxx:9001/siebel/v1.0/service/Automation Rest Service/GetTestRunId?ClientName=XXXXX
INFO :: RUN-ID : 1-RLA6 is Picked.
INFO :: SOAP URL :: https://xxxxxxxx:9001/siebel/app/eai/enu?SWEExtSource=WebService&SWEExtCmd=Execute&WSSOAP=1
INFO :: Starting Attachment Download for RUN-ID 1-RLA6
200
INFO :: XML File C:\DISA\DesktopIntSiebelAgent\plugins\SiebelTestAutomation\TestExecutions\1-RLA6\batchconfig.xml downloaded successfully.
INFO ::Suite File C:\DISA\DesktopIntSiebelAgent\plugins\SiebelTestAutomation\TestExecutions\1-RLA6\Scripts\siebel.csv downloaded successfully.
INFO :: Optional Resources folder not found in attachments to download. Process Will Continue...
INFO :: Optional Dataset file not found in attachments to download. Process Will Continue...
INFO :: Attachments Downloaded Successfully for RUN-ID :: 1-RLA6
INFO :: Following RUN-IDs are picked - 1-RLA6
Starting Siebel Test Automation Execution...
Replication Setup
-1. Setup Test Automation and DISA setup as outlined Innovation Pack 17.0 Siebel Test Automation(2396540.2)
-2. Run the following command from DISA
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 |
Cause |
Solution |
References |