There are a variety of different places to find support of any issues you may encounter or questions you may have. Firstly, you can speak with the engineering team directly using the chat feature when you first open mabl, which should appear at the bottom lefthand corner of the screen.
In addition, you can also email us directly at [email protected] if you would prefer.
mabl is an automated testing service that is powered by machine intelligence. You can use mabl to identify regressions in the functionality of your web sites applications.
When you set up your first application, mabl begins to execute default tests that apply to most web sites and web applications. In order to complete these tests, mabl only needs to know where to access your application (URL) and, if applicable, which credentials to use to log in. The default tests are smart enough to figure out how to log in and traverse links for most applications.
Beyond these default tests, you’ll want to train mabl how to test your application using the Chrome Extension.
mabl accesses your application via Chrome browser sessions running in compute containers and virtual machines hosted on cloud infrastructure. mabl follows tests to complete specific operations, captures the output, processes the results, and feeds information and insights back to you via the mabl application.
Please refer to the pricing page for more information on our pricing structure.
When you create an application, mabl adds two default tests and corresponding plans automatically.
The first test is a basic smoke test that visits the base URL of your environment and logs in, if applicable. The plan is configured to test that test every 30 minutes and any time you notify mabl of a deployment of the application to a particular environment.
The second test is a crawl through your entire application. With this test, mabl loads your base URL, visits each of the linked pages, visits each of the links on those pages, and so forth. mabl will follow up to 50 layers of links within your domain. It will also load external links but it will not “crawl” pages outside of your domain. The plan for that test specifies that it will be tested every 24 hours and any time you notify mabl of a deployment of the application to a particular environment.
Yes! mabl maintains native plugins for Jenkins and Bamboo. Likewise, mabl provides a REST API that you can call from your CI/CD tool to notify mabl of new deployments. These deployment events will trigger the execution of any test policies that are configured to fire when a deployment occurs. You can find the API keys and a CURL command builder for your account on the Settings page within the mabl web interface.
In addition, mabl can integrate with webhooks. You can find more information about them here in the docs.
Yes! mabl provides a Chrome extension that you can use to define tests that are specific to your application. You can then define Plans to test those tests on a schedule or when a new deployment occurs.
Yes! mabl lets you retrain and edit your tests via the main dashboard/monitor page. You can edit most steps, and if not it's simple to redo the step! To find our more, you can visit the edits docs page.
By default, mabl provides insights when:
- mabl is unable to login using credentials that you provided for your test account.
- mabl is unable to load your homepage or login page.
- The load time for your application home page is currently faster or slower than usual.
- The execution time for a given test is currently faster or slower than usual.
- There are new broken or fixed links within your application.
- mabl detects an unexpected visual change on your page.
- Your plans change from passing to failing, and the reverse.
Many of the insights that mabl provides are based on learned models of your application. The quality of the models improve automatically as mabl executes more tests. mabl also asks for your feedback in the user interface for each insight type and uses that feedback to improve its model for your particular environment.
Yes! You can configure mabl to send any new insights to any channel or team member on Slack. Slack integration is available via the Settings screen within the mabl web interface.
Yes! mabl will adapt to test your application, regardless of whether it's an SPA or not. You won't have to test your SPA any differently than you would any other application.
If you experience conflict issues between your application and the floating mabl Trainer during testing, such as maintaining focus on the correct element, we recommend using the Chrome DevTools Trainer. Unlike the floating mabl Trainer, the DevTools Trainer is not embedded in your application during testing. Feel free to reach out to the team in-app or at [email protected] with any further questions.
mabl is a multi-tenant SaaS solution. It cannot be deployed on-premise or in a single-tenant environment today. However, you can use mabl Link to test on-premise environments.
You can use mabl Link to set up a secure tunnel between mabl's test systems and your internal environments. Alternatively, you can create firewall rules to permit inbound traffic from mabl's IP addresses, which you can find them under the "Settings" page and the "Networking" tab.
mabl takes the security very seriously. For example:
- All mabl systems use SSL encryption to encrypt all data in transit.
- Customer data is encrypted at rest using customer-specific encryption keys (AES-256).
- All keys are managed by a widely-used hosted key management service.
- The mabl application is deployed on cloud infrastructure that maintains compliance with a wide variety of security and privacy standards, including SSAE16 / ISAE 3402 Type II, PCI/DSS, and many more.
- mabl integrates with popular single sign-on providers in order to support centralized identity and access management.
- The mabl service and systems undergo regular penetration testing.
- The mabl service, systems, and components are automatically scanned for known vulnerabilities.
- All mabl employees are required to participate in security training.
- All mabl data is stored in the United States.
mabl only supports web-based applications today.
mabl only supports applications that can be accessed via Chrome, Firefox, IE 11, or Safari today.
mabl runs tests on Chrome, FireFox, Internet Explorer 11, and Safari today!
Hover over the browser icon of any test to see the specific browser version the test ran on. Additionally, you can view the browser version for a specific test run by clicking "View more" from the header at the top of the page.
mabl supports multi-user Organizations. Invite other team members to share an Organization from the Settings > Invitations screen. Once the Invitation is accepted, the user will be joined to the Organization.
Yes, you can restrict the link crawler to only those pages that are under your root URL by adding a parameter to the "Visit all linked pages within my app" test on the plan edit form. The parameter is of type "mabl Parameter", parameter name is "Use strict URL prefix", parameter value is "True".
See the "Restricting the crawler to a specific application" document for step-by-step information.
mabl will stop a test early if it runs for too long, so you don't need to worry. You can also stop a run of a plan by clicking the top button on the run column of the "plans" page.
At this time, mabl can record and play back a limited number of keypress events including: alphanumeric characters, Enter, Tab, Backspace, and Delete.
mabl automatically retries steps every 100 milliseconds for up to 30 seconds. This usually allows pages to load, or other actions to complete. If a process takes longer than 30 seconds, you can manually add a wait step to your test.
Be sure to check that the mabl Trainer is set to record, you'll see a glowing red
Rec. if it is.
mabl supports the vast majority of interactions with webpage elements, as long as the page itself is comprised of an HTML DOM. If mabl isn't recording your interactions with your page that does have a DOM, be sure to confirm that you're not testing shadow DOM elements or the contents of an SVG. Read to the two sections below to learn more.
mabl does not support testing of shadow DOM elements at this time. Only interactions with elements that appear within the regular DOM will be recorded and executable.
Currently, mabl cannot interact directly with SVG elements. However, a very simple workaround allows mabl to find the element you're looking for. Instead of interacting directly with the SVG element, you will need to target the element that contains the SVG. The mabl team is currently working on functionality that will solve this issue without needing a workaround, but in the meantime, this solution will solve any issues with SVG elements that may occur.
Unfortunately, there isn’t a way to use our auto-login for cases where there are three login fields today. Currently, the only approach available today is to disable auto-login and manually step through the login within your trained test.
At this time mabl is unable to access applications behind two-factor authentication. If you wish to test your application behind this authentication, you will need to disable it for mabl to properly access your app.
If you can generate a Bearer Token from your identification provider, then you can pass that authorization header to all test browser requests when starting tests from the mabl CLI overview. For example, users of Google's Identity Aware Proxy can generate tokens from service accounts and pass them to mabl via the mabl CLI with the
mabl crawler traffic adds the following headers for traffic identification:
“User-Agent” : … “Mabl/0.1” (contains)
“X-Mabl-Agent” : “Mabl/0.1”
How do I engage with mabl and other users on feature requests, bug reports, new releases, tips and tricks, and more?
"Journey" is just an old term for tests.
Updated about a month ago