Persist Login
Avoid having to login via the UI each time a test is run
Most tests need the user to login to a specific user account. You can achieve this by logging in manually every time the test is run, performing the necessary clicks and typing to login via the UI, but this means the test will take longer to run and will break if the login flow changes. A better solution is to use our 'login storage state' feature.
If you are setting up a new test, and have logged in to the user account, then you can add a "Save Login Storage State" step. This will save the local storage from the remote browser against the test case. When the test is run, we will skip the initial login steps and instead just load the state into the browser, meaning the user will already be logged in.
There are a couple of important things to remember:
The video at the top of this guide provides more explanation on each of the above and an example. We strongly recommend that you watch this video before using this feature.