How to set up your mabl workspace to achieve coverage at scale
If you just created a mabl workspace and aren't sure what to do next, this is the place for you. This guide walks you through the steps needed to set up a successful mabl workspace and achieve coverage at scale.
At a high level, you can take the following steps to set up automating testing for your application:
- Create an application and environment
- Create some tests
- Add tests to plan and set it to run automatically
Creating an application and environment
Applications define what you are testing, such as a web application, and they are associated with one or more environments. Environments represent where your team deploys code, such as Dev, QA, and Prod.
As a team, there are likely multiple applications that you have to test. Create an application in mabl for each application that you want to test.
For example, in our own internal mabl-testing-mabl workspace, we have the following applications defined:
- mabl app: our main application
- Sandbox: example test application for experimenting with mabl
- Help docs: our support documentation for how the product works
- mabl.com: our main landing page
For our environments, we have Preview, Development, and Production. These environments line up with our software development lifecycle.
Configure a URL for an application in each environment that it is associated with. In the following example, there are two applications and three environments: Dev, Preview, and Prod. The "Example app" has a URL for each environment, whereas the "Acme app" only has a URL for Dev and Prod.
The layout on the Applications page is arranged as follows:
- Application names on the left axis: Acme app and Example app
- Environment names on the top axis: 1. Dev, 2. Preview, 3. Prod
- Application URLs for each application appear below the environment to which they are deployed.
For more information on creating applications and environments, check out this guide.
Don't have an app to test?
If you don't have an application to test against, try the following example:
- Create an application for the mabl Sandbox:
- Create an environment named "Demo"
After you create at least one application and environment, the next step is to start testing!
For your first browser tests, we recommend creating simple tests that validate core functionality, such as:
- Basic smoke test
- Account signup
For your first API tests, we recommend creating short tests that validate that your API endpoints return the expected results.
For more information on creating tests, check out our getting started guides for creating the following test types:
After creating a few tests organized around a common theme, collect them together in a plan. Plans are where you configure your automated testing strategy. To configure your plan to run automatically, set a trigger to run the plan on a schedule.
For more information on the different ways to organize plans, click here.
Set up integrations
By embedding mabl into your existing tools, you can integrate testing into every stage of development, increase the visibility of issues among your team, and speed up the time to resolution. Some of the integrations offered by mabl include:
- Jira integration
- CI/CD integrations
- Slack and Teams integrations
With the Jira integration, you can create Jira tickets directly in mabl and speed up the process of identifying and resolving bugs.
Mabl offers native CI/CD integrations, allowing you to integrate your automated mabl tests into your existing CI/CD pipeline so that you can catch and fix issues earlier in the development cycle.
Slack and Teams integrations
Using mabl's integrations with Slack and Microsoft Teams, you can surface key failures and significant changes in your mabl tests right where your team works.
In mabl, you can invite an unlimited number of users to your workspace and configure their permissions according to the type of user: owner, editor, or viewer. Once you've invited some teammates, you can start collaborating on tests! Useful tools for collaboration within mabl include the activity feed and branching.
As your mabl workspace grows, the activity feed can help you monitor recent changes and serve as a reference for conducting regular reviews with your team.
Workspace members can make isolated changes without impacting each other's work with branches, and when it's time to merge, teammates can use commenting to resolve issues collaboratively within mabl.
Updated about 1 month ago