Use plan credentials as variables

When adding a plan, if you provide a set of credentials, mabl will exercise the auto-login feature; that is, mabl will try to figure out how to log into the app on her own. But if you want to train her instead, the app credentials are now accessible in the trainer as variables, and you can apply them to login fields.

Use app credentials in the training extension

Use app credentials in the training extension

Tip

Remember to remove the auto-login flow from the journey if you train mabl to log in this way. You can do this from the Journey Details page.

Your credentials are stored separately from the journey script. They are encrypted at rest and in transit. You can even configure multiple plans that supply different credentials to the journey at runtime.

App credential fields in the Edit Plan form

App credential fields in the Edit Plan form

Credential variables are examples of a new class of variables that are configuration related and automatically defined. You cannot edit the values of these variables, but you can use them like any other variables, including in a generated variable pattern (e.g. "{{@app.url}}") or in a custom JavaScript.

Currently the following variables are supported:

  • "app.url" - URL of the app under test
  • "app.username" - App login username specified in a plan
  • "app.password" - App login password specified in a plan

If you want to use these variables in a custom JS step, you may reference them as:

  • "mablInputs.variables.web.defaults.url"
  • "mablInputs.variables.web.defaults.credentials.username"
  • "mablInputs.variables.web.defaults.credentials.password"