Siebel Test Automation Folder

The Siebel Test Automation folder structure contains the required folders for executing the csv script. The Framework folder contains all the required JARS and library files. The following folder structure is available when you install DISA.

Folder	File Type	Comment	Execution
Framework\	Exe	Do not modify	Contains necessary Exe files which are used in the SiebelTestAutomation Framework
Framework\	Lib	None	Contains necessary Library files (JAR files) which are used in the SiebelTestAutomation Framework
Framework\	Perl	None	Contains necessary Perl scripts which are used in SiebelTestAutomation Framework
Framework\	SiebelTestAutomation.jar	None	Compiled executable JAR which drives KWD execution
Extensions	.jar	CustomExtension KeywordActionHandler implementations	Placeholder for CustomExtension JAR files.
Reports	N/A	Post- execution file	The folder gets created post execution, generates execution results for review. Note: For batch runs, this folder is created under the SiebelTestAutomation\TestExecutions\ <RunId>\ folder.
Resources\	N/A	Contents of Resources.zip are unzipped into this folder.	Note: For batch runs, this folder is created under the SiebelTestAutomation\TestExecutions\ <RunId>\ folder.
Resources\	fileupload	Script authoring file	Folder containing user developed files needed for fileupload.
Resources\	inboundwebservicecall	Script authoring file	Folder containing user developed files needed for inboundwebservicecall.
Resources\	invokeperl	Script authoring file	Folder containing user developed files needed for invokeperl.
Resources\	toolsconfig	Script authoring file	Folder containing user developed files needed for toolsconfig.
Resources\	serverconfig	None	Folder containing user developed files needed for serverconfig keywords.
Scripts\	Samplescript.csv	None	Place holder for csv scripts. Note: For batch runs, this folder is created under the SiebelTestAutomation\TestExecutions\ <RunId>\ folder.
TestExecutions\	N/A	Batch runs.	Folder where individual batch run folders are created – each folder is named according to the "Run Id" (row id) of the test execution record.
SiebelTestAutomation\TestExecutions\ <RunId>\batchconfig.xml	XML (.xml) file.	Pre-setup file	XML File which contains the configuration details of the execution (URL, username password, script location). The batchconfig.xml file will be copied by the Jenkins scheduler if it is an STE run. The unitconfig.xml file will be used for the UPT run.
SiebelTestAutomation\TestExecutions\ <RunId>\User_opted_operation.txt	Text (.txt) file.	Text file	Text file which contains information like Pause, Resume and abort. The user has the option to Pause/Resume/Abort the current execution by updating the value in the User_opted_operation.txt file.
SiebelTestAutomation\TestExecutions\ <RunId>\Log_randomnumber.log	Log (.log) file.	Log file	Text file which contains log messages by Framework for debug purposes.