Environment variables

Select a configured environment with --env <name> or the test’s defaultEnv. The --env flag chooses the environment; it does not assign variable values. Within that environment, Momentic loads variables in this order. Later sources override earlier values with the same name:

envVariables, including values loaded with fromFile.
The envFile.
The enclosing shell, when inheritFromShell: true.

See environments for the full schema.

Secrets

For passwords, API tokens, and other secrets, prefer a .env file or shell or CI environment variables over inlining values in momentic.config.yaml. See Secrets for the recommended patterns.

Reserved variables

Momentic sets these at runtime. Access them via {{ env.NAME }}:

Variable	Description
`BASE_URL`	Base URL of the current environment
`CURRENT_URL`	URL of the page being tested
`ENV_NAME`	Name of the current environment
`TEST_NAME`	Name of the test being executed

BASE_URL and CURRENT_URL apply to web tests. Mobile tests use an app artifact rather than a browser URL.

Access variables in tests

Use the templating syntax anywhere a step accepts a string:

- type:
    text: "{{ env.USERNAME }}"
    into: Email field

Access env.VARIABLE directly inside a JavaScript step.

Set variables at runtime

Use setVariable inside a JavaScript step to write a variable:

setVariable("OTP_CODE", "123456");

Use the Save to environment variable option on any step with a return value (e.g. AI extract, JavaScript).

​Secrets

​Reserved variables

​Access variables in tests

​Set variables at runtime

Secrets

Reserved variables

Access variables in tests

Set variables at runtime