Mabl is designed to help development organizations deliver modern software quality with features that help development teams confidently deliver scale automated testing while protecting sensitive information. These features, such as mabl credentials, have long been part of mabl’s unified platform and are critical for enterprise teams that need a robust test automation platform that can meet their long-term quality needs.
Whether you’re a new mabl user or a mabl University certified expert, this guide will help you make the most of mabl credentials in your test automation strategy.
Mabl credentials are a unique type of variable in mabl that allow software testers to reduce the risk of exposing sensitive information. These variables can be used as part of local and cloud-based browser tests, depending on the credential type, and are typically used to validate login flows.
The values of mabl credentials are encrypted with a customer-specific encryption key before getting added to mabl’s database, so customers can be confident that their data is protected.
There are four types of mabl credentials, which give mabl users flexibility across local and cloud-based test runs.
Basic credentials consist of a username and password. They can be used for training and running tests locally and in the cloud.
Basic credentials with MFA consist of a username, password, and MFA authenticator secret code. They can be used for training and running tests locally and in the cloud.
Mabl users can update and clear the secret code for basic credentials with MFA, but they cannot retrieve an existing secret code.
Cloud credentials consist of a username and password. They can only be used for cloud runs.
The username and password may be updated, but passwords can never be retrieved once the credentials are saved.
Cloud credentials with MFA consist of a username, password, and MFA authenticator secret code. They can only be used for cloud runs.
Mabl users can update the username, password, and secret code, but they cannot retrieve an existing password or secret code once it has been saved.
All types of mabl credentials can be created by clicking on Configuration in the left-hand navigation and selecting the Credentials tab. Note that due to their sensitive nature, only owners and editors of a workspace can create mabl credentials.
Mabl credentials can be used to train new or existing browser tests, empowering QA and developers to validate the user experience across important security flows. It’s important to note that tests can only be trained with basic credentials or basic credentials with MFA, not cloud credentials or cloud credentials with MFA.
Mabl credentials appear in the Trainer as app.defaults.username and app.defaults.password.
Training with mabl credentials
If a new browser test is part of a plan, where one or more tests run in sequence or in parallel, the test will use credentials assigned at the plan level. If the new browser test is not part of a plan, testers need to select credentials in the expanded optional configurations section.
When training an existing browser test, mabl users can configure the training session to use a specific set of credentials in the edit test configuration modal. Note that credentials set at the plan level override credentials set at the test level and that only one set of mabl credentials can be assigned to a plan. All tests that use mabl credentials in a plan run use the same set of credentials.
Cloud credentials are ideal for test environments that access sensitive data since they help protect user data by limiting access to sensitive data like passwords. Once cloud credentials are saved, the password can be updated, but never retrieved. Lime basic credentials, cloud credentials can be created with or without MFA authenticator secret codes. Unlike basic credentials, however, cloud credentials cannot be used for local ad hoc runs or to train tests.
Mabl allows development teams to easily convert basic credentials to cloud credentials for stronger data security across existing tests and plans that use mabl credentials.
Converting basic credentials to cloud credentials takes just a few steps:
Converting basic credentials into cloud credentials
With mabl, development teams have the power of a low-code platform backed by the scalability and efficiency of cloud for more comprehensive testing that meets the demands of DevOps. Basic and cloud credentials are one more way that mabl empowers quality teams to improve test coverage and protect sensitive information.
See how your team can deliver modern software quality with mabl's unified test automation platform by enrolling in a 14-day free trial.