With help of the Validation feature you can test whether the format of your recording is correct, as well as check if the login attempt succeeds without the need to perform a full scan.
How does it work?
We retrieve the file with the recording and try to sign in to perform the sanity checks via our Dublin IP's (currently the validation feature does not take into account the set Scan Region from your Team Settings). If your site switches to another version depending on where it is being accessed from, try updating the "Target: " command in the file to e.g. its .ie version and running another validation with it.
When performing the validation, we use all headers (including the User-Agent one) from your Application Scan Settings, cookies and scope provided.
How long does it take?
The normal runtime of a validation scan is 3-10 minutes depending on the size of the Trail file and the current queue in the system.
The successful validation will display the "Success" status:
If the validation failed, click on the exclamation mark icon to check the error logs and use the troubleshooting guide available at Recorded Login: Trails service documentation to correct the recording.
The example below shows that the validation fails at step 2, due to a blank tab being opened when recording the login sequence:
In this case you can either record a new sequence making sure the blank page is not opened (check this article to see what things to keep in mind when recording your file) or remove the failing step from your file and re-upload the corrected file to your account.
If you need any assistance, drop us a line at firstname.lastname@example.org.