- Credentials are a pain to secure and maintain. If you use mabl’s auto-login feature, you can take advantage of our enterprise-grade key management service, and you can easily update credentials across journeys.
- If you use auto-login, take care to avoid logging in during your training session; this will result two attempts to log in, and the second one will result in a failed test.
- When using the feature, it helps to set your Plan's URL to the login page. This will greatly speed up your initial test execution time, as mabl won't have to search for a login form.
- It may also be helpful to add a short wait step directly after you login, to make sure the webpage has time to load before executing. Please see the "Adding wait steps with the mabl trainer" document for more information.
- Your local storage may contain settings that affect the application state. mabl’s test machines will not have that state. Navigate to the “Application” tab in Chrome developer tools and clear application storage before you start training.
- Start by training your journey against any application environment, just create a plan and type in a new URL to test.
- You can include that journey in separate plans for QA, staging, production, etc.
- You can access this feature via the toolbar within the trainer.
- This makes it easy to create a test that looks for elements by xpath or CSS selector.
- During training, the trainer will automatically highlight any elements that match your query.
- You can enable “record hovers” in the mabl trainer.
- When enabled, this adds a hover step each time your mouse hovers over an element.
- Given that this can add many steps (which, in turn, can add significant test execution time), you shouldn’t enable it unless you are explicitly attempting to capture a hover event.
- You can define and use variables via the toolbar within the trainer.
- You can, for example, use a variable that will always insert a random string into a field.
- This can help you work around uniqueness requirements within your application if you’re not always setting your test environment back to a pristine state between runs.
- This is a way to avoid testing your marketing site, docs, et.
- You can set the parameter for any plan that includes the “Visit all linked pages” journey.
- It is easy to submit deployment events and retrieve plan results via mabl API
- Information is available via Settings --> APIs.
- This triggers any plans that are scheduled to run on deployment.
- mabl also maintains a native Jenkins plugin.
- All requests feature the
- All User agent strings have a custom operating system property (contains
Mozilla/5.0 (X11; Linux mabl) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36
- All traffic emerges from the mabl static IP address block, unless the plan environment uses mabl Link
Click here to jump back into mabl to start testing!