The TEDAM automation process starts with the creation of test scenarios in the Tedam Face interface. When creating the test scenario, it is critical that the scenario steps are atomic. When writing a test scenario, it is important that a single mouse movement corresponds to a single scenario step.
Select the snapshot files related to the test scenario and upload to the system. Associate the test scenario steps with the related snapshot file. In this way, the user can continue the process by selecting the components to be interacted through the interface connected to the test step.
Currently available test step types;
ButtonClick: In snapshot file contains a list of clickable components and selected which component the user will click.
Formfill: In snapshot file contains a list of text fillable components and user value writes the value to the writable component.
Verify: Verifies the data on the screen.
DoubleClick: In snapshot file contains a list of double clickable components and selected which component the user will double click.
Wait: Provides to wait otomation according to entered parameter.
The user can combine test scenarios with TestSet in small meaningful groups.
For example, when ordering, first of all, the product to be ordered may need to be create with automation in the system.
In this case, it can be ensured that the product creation and ordering scenarios can be combined in a testset for successive operation.
Job is the component where the test sets are classified and the clients to which they will run added.
When a job is created it need following components:
-Test Sets which will be executed,
-Agent which run jobs,
-Environment which job runs on it.
What is the Tedam Agent?
How to define Environment?
It is the screen where the active jobs can be started and stopped. Whether jobs run or not are monitored currently.