Hide Sensitive Environment Data Across Every Test
Stop hardcoding passwords, API keys, and tokens in your test scripts. Store each credential once in a secure Environment, mask the value, and reuse it everywhere — without changing the way your tests run.
Hardcoded secrets slow you down.
Difficult to maintain
The same secret is copy-pasted into dozens of files. Rotate it once and every test breaks.
Increased security risk
Plain-text credentials leak through commits, screenshots, run logs, and shared reports.
Harder to scale
Every new environment or teammate means re-pasting secrets and hoping nothing drifts.
One secure place for every credential.
Store once
Add each password, key, or token to the Environment a single time as a named parameter.
Protect
Set the type to Password or Vault and the value is masked — in the editor, logs, and reports.
Reuse everywhere
Reference the parameter by name from every test, suite, and run — rotate it in one place.
Secure a secret in three steps.
Move a credential out of your scripts and into a masked environment parameter — your tests keep running exactly as they did.
Add it to the Environment
Give the credential a parameter name and value in the Environments editor — no code changes.
Set the type to Password
Switch the Parameter Type from Text to Password or Vault. The value is instantly masked.
Reference it in any test
Call the parameter by name across every test and run. The raw value never appears in logs or reports.
Built to keep test data private.
Masked values
Password and Vault parameters hide the raw value behind dots the moment you save it.
Password & Vault types
Choose Password for everyday credentials and Vault for your most sensitive, centrally-managed secrets.
Reuse across suites
One parameter powers every test that needs it. Update the value once and every run picks it up.
Table & JSON views
Manage parameters in a clean table or edit them as JSON — whichever fits your workflow.
Masked in logs & reports
Hidden values stay hidden in run logs, screenshots, and shared reports — no accidental leaks.
Rotate in one place
When a secret changes, edit the single environment parameter and every test uses the new value.
Secure your test credentials without changing the way your tests run.
Hiding a value changes how the credential is stored and shown — never how the test executes. Your existing suites keep passing while your secrets stop leaking.
- Raw values never live in the test body
- Masked in the editor, run logs, and reports
- One source of truth per environment
Hiding environment data, answered.
What does hiding sensitive environment data mean in ContextQA?
It means moving passwords, API keys, and tokens out of your test scripts and into a secure Environment. You store each credential once as a parameter, set its type to Password or Vault so the value is masked, and reference it by name inside your tests. The real value is never written in the test body.
How do I mask a credential in an environment?
Open Environments, add a parameter with a name and value, then change its Parameter Type from Text to Password or Vault. The value is immediately hidden behind dots in the editor, and it stays masked when the test runs and in the run logs and reports.
Do I have to change my tests to use hidden data?
No. Your tests reference the parameter by name, exactly as before. Hiding the value changes how the credential is stored and displayed, not how the test runs, so you can secure existing suites without rewriting them.
Can one credential be reused across many test cases?
Yes. You store the credential once in the Environment and reference it from every test case, suite, and run that needs it. When the secret rotates, you update it in one place and every test picks up the new value automatically.
What is the difference between the Password and Vault types?
Password masks the value in the editor and reports while keeping it available to the test at runtime, which suits most credentials. Vault is used for the most sensitive secrets that should stay protected and centrally managed. Both keep the raw value out of the test body.
Are hidden values shown in run logs or reports?
No. Values stored as Password or Vault stay masked in the editor, in run logs, and in reports, so secrets are not exposed to anyone reviewing test results or sharing a report.
Keep your secrets out of your tests.
See how ContextQA stores every credential once, masks it, and reuses it across your whole suite — without touching the way your tests run.
