-
Notifications
You must be signed in to change notification settings - Fork 4
How to define Environment?
You should know the job parameter and client command before define environment.
A sample "client command" used in WEB products is shown follow:
java -jar L:\lib\TEDAMSelenium\tedam-selenium-1.0.jar browser!equals!$browser url!equals!$url timeRecording!equals!$timeRecording testSetId!equals!#testSetId testCaseId!equals!#testCaseId #testSteps
Client command consists of two parts:
- Executable file information of the application that the user wants to run
- Parameter names and values to be pass to the application
When we look at the example command, the application that the user wants to run is "tedam-selenium-1.0.jar".
The parameters required for this jar file to work:
"browser!equals!$browser url!equals!$url timeRecording!equals!$timeRecording testSetId!equals!#testSetId testCaseId!equals!#testCaseId #testSteps"
When we look at the these parameters, there are two types of parameters. The parameters which start with # are pre-defined parameters that are in TEDAM. The parameters which start with $ are the parameters that the user wants to generate different parameters for each job. These are called "Job Parameters" in TEDAM.
These are the “job parameter” groups of values selected by the user for each job.
For example, “chrome test” environment can be defined with values "browser:chrome, url:test.logo.com.tr, version:1.3, timeRecording:true"
; also “ie test” environment can be defined with "browser:ie, url:test.logo.com.tr, version:1.3, timeRecording:true"
values.
The user can run any application with desired parameters through dynamic structure of the environment logic.