For any executions with “BLOCKED”, you will see an icon to access the Remediation Details
You will be able to select your preferred elements for setting a new baseline
|1||Baseline||An image defines the expected appearance of your application at each step.
Note: In this case, the baseline is on Galaxy Note 9
|2||Screenshot||An image defines an output of a specific test steps on other devices. Moreover, you can inspect all elements within an image to set a new baseline for your test case.
Note: In this case, the screenshot is on Galaxy S6
Select the remediation’s scope and submit
|Comparison Level||Scriptless Automation provides you an option to test the UI in 4 different comparison levels:
Exact: Compare and do not allow any difference (pixel-to-pixel comparison)
Strict: Compare and allow minor differences (up to the equivalent of 5% difference)
Relaxed: Compare and allow significant differences (up to the equivalent of 20% difference)
Ignored: Take the best matching element regardless there are similarities
|Scope||Scriptless Automation provides you an option to select the scope to apply the “new baselines on”:
|Noticed||For any remediations that could not remediated (Application crashed, missing element, etc.), you can this button to mark an execution as failed and it will be excluded for the next re-run.
Note: In the future, we will implement the Create Defect to allow report bug instantly on our platform
|Submit||After you click the “Submit” button, the remediation will be applied right the way and the giving execution will be automatically run again.|
You can access back your submitted remediation