At mabl, we believe that testing is a team sport. When everyone contributes to the quality of your app, your team can build test coverage faster and catch issues earlier.
Use this checklist to help your team collaborate effectively as your testing scales:
- Invite your team and give them the right access
- Empower your team to build and understand tests
- Connect mabl to your existing workflow
- Integrate mabl into your CI/CD
- Review tests on a regular basis
Note
Most of these checklist items require workspace owner permissions.
Invite your team and give them the right access
Collaboration starts with inviting teammates to your mabl workspace. Visit the teams page - Settings > Team - and choose an appropriate workspace role for each person you are inviting.
| Role | Description |
|---|---|
| Editor | Choose editor for anyone who needs to create or update tests. |
| Viewer | Choose viewer for stakeholders who only need to see results and won't be creating tests. |
| Owners | Reserve the owner role for people who will manage workspace settings integrations, and user roles and permissions. |
SSO login
If your team uses an SSO provider, you can also set up SAML to simplify login.
Empower your team to build and understand tests
When team members can interpret test results on their own, fewer questions escalate to test creators, and the team builds shared ownership over quality. To build coverage faster, equip your team with the tools they need to create tests and understand test results:
- Encourage your team to complete self-guided training lessons and skills certifications in mabl U.
- Share relevant mabl help resources with your team for creating tests, running tests, and understanding results.
Connect mabl to your existing workflow
Notifications surface failures in the tools your team already uses so that issues don't go unnoticed. To streamline your testing workflow, integrate mabl with the tools your team already uses:
- Set up the Slack or Teams integrations to immediately notify your team when a test fails.
- Set up the Jira integration to link tickets to mabl tests for better traceability.
Integrate mabl into your CI/CD
To reduce the burden of manual work, integrate mabl into your CI/CD pipeline. Set up tests to run automatically before merging changes or after deploying code to a new environment.
Integrating mabl with your CI/CD tool gives everyone on the team better visibility into the quality of your app. If there are any issues that require deeper investigation your team can follow up on the using the detailed test output in the mabl app.
Review tests on a regular basis
Tests that drift out of sync create noisy failures. To ensure your results remain relevant, review tests on a regular basis. Work with your team to establish shared guidelines for creating tests, and set up regular workspace audits to ensure your testing strategy remains effective.
Account admins can also track adoption across your workspaces with the account-level engagement dashboard and spot quality trends with the account-level coverage dashboard. Together, these dashboards give you a cross-workspace view of how teams are testing in mabl.