Accessibility check
A step in a browser test that checks for accessibility violations for a page or specific element in your application.
Activity feed
A page in the mabl app where you can filter historical user activity information across the workspace.
Application
Applications are used to organize functionality, tests, and results into sets that are relevant to your organization. Many people choose to define one application for each unique product that they offer to their customers, while others choose to define applications at a more granular level. The former approach is more common with products that are supported by a single, relatively small development team, whereas the latter is more common with more feature-rich products that may be supported by multiple development teams.
Assertion
An assertion is a statement about your application that you would like mabl to confirm is true when running a test. For example, when training a browser test, you might assert that a text field should have a certain value at a particular point in a test run.
Branch
Branches in mabl represent lines of development. By default, every workspace starts with a master branch. If you want to update tests or flows without impacting the main version, you can save your work to a test branch.
Credentials
Credentials provide mabl with authentication information for the purpose of executing a test.
Database connection
A database connection provides a way for client software to communicate with database server software. In mabl, you can configure database connections to send queries during web and mobile tests.
Deployment event
A deployment event is an event that triggers all plans in mabl that match specified conditions to execute. These events are often triggered from a CI/CD pipeline but can be manually triggered as well.
Environment
An environment is a resource to which mabl connects in order to execute a test. To illustrate, an application might have two environments; one for development, which is accessible via https://dev.example.com, and one for production, which is accessible via https://app.example.com.
Flow
A flow is a set of sequential steps that mabl must execute in order to verify that a particular part of a test is functioning as expected. Flows can be reused across multiple tests.
Insights
Insights are updates that notify users of significant changes in their application, such as auto-heals, broken links, or an increase in page load time.
Intelligent Wait
Intelligent Wait is a process by which mabl learns about the expected timing of your web app to ensure it is in the correct state before interacting with it.
Label
A label is a description used to organize and filter plans, tests, and flows.
Link crawler
The link crawler is a test that informs you of any potentially broken links in your web application. The output of the link crawler test also serves as the basis for calculating test coverage in your application.
mabl Link
mabl Link is a secure tunneling solution that your team can use to test against private sites and endpoints.
mabl CLI
The mabl CLI is a command-line tool that you can use to integrate mabl into your CI/CD pipeline and developer workflow.
Plan
A plan specifies how mabl should run tests. It tells mabl which application to test, which credentials to use (if applicable), which tests to run, which environments to test against, and when the tests should be executed.
Scenario
A scenario is a set of values, a specific row in a DataTable to be precise, that are passed a test as part of data-driven testing. The first column in a scenario is used to name that particular row, which will be shown wherever a test that uses that scenario is run.
Snippet
A snippet is a piece of JavaScript code that runs in a test to support custom use cases. Snippets may be saved for one-time use or reused across multiple tests.
Step
An action that mabl takes during the execution of a flow or test. Examples include click, wait, enter text, create variable, assert, etc.
Test
A test is the set of instructions that mabl must execute in order to verify that your application is functioning as expected. For example, in a browser test instructions could include visiting a particular URL, clicking on a given field in a form, entering text, clicking on a button, verifying that a field has a certain value, verifying that an object loads, and more. These were previously called "Journeys".
Resource group
Resource groups establish granular role-based access control in a workspace. Workspace owners add specific resources to the resource group, such as sensitive credentials, and assign roles to specific workspace members.
Visual baseline
A visual baseline is a screenshot used as a point of comparison for visual change detection. Visual baselines may be static or, if visual change learning is enabled, dynamic.
Visual change learning
Visual change learning is a setting managed at the plan level that creates dynamic visual models for browser tests and generates visual change insights when a visual change is detected.
Workspace
Workspaces are used to group applications, environments, credentials, tests, plans, and more. into a set for the purpose of providing appropriate visibility and access control. A workspace is the broadest grouping within the mabl application. Users can belong to one or more workspaces.