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.
The same secret is copy-pasted into dozens of files. Rotate it once and every test breaks.
Plain-text credentials leak through commits, screenshots, run logs, and shared reports.
Every new environment or teammate means re-pasting secrets and hoping nothing drifts.
Add each password, key, or token to the Environment a single time as a named parameter.
Set the type to Password or Vault and the value is masked — in the editor, logs, and reports.
Reference the parameter by name from every test, suite, and run — rotate it in one place.
Move a credential out of your scripts and into a masked environment parameter — your tests keep running exactly as they did.
Give the credential a parameter name and value in the Environments editor — no code changes.
Switch the Parameter Type from Text to Password or Vault. The value is instantly masked.
Call the parameter by name across every test and run. The raw value never appears in logs or reports.
Password and Vault parameters hide the raw value behind dots the moment you save it.
Choose Password for everyday credentials and Vault for your most sensitive, centrally-managed secrets.
One parameter powers every test that needs it. Update the value once and every run picks it up.
Manage parameters in a clean table or edit them as JSON — whichever fits your workflow.
Hidden values stay hidden in run logs, screenshots, and shared reports — no accidental leaks.
When a secret changes, edit the single environment parameter and every test uses the new value.
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.
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.
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.
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.
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.
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.
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.
See how ContextQA stores every credential once, masks it, and reuses it across your whole suite — without touching the way your tests run.
What you test
Catch hallucinations and drift before users do
SAP, Oracle, Workday & custom ERP
Browser automation across every engine
Native iOS and Android coverage
REST and GraphQL validation
CRM workflow automation
Enterprise application coverage
See what a code change breaks before merge
How you test
Plan, track, and manage every test
Tests repair themselves as code shifts
Pinpoint why a test broke, instantly
Catch unintended UI change
Load and stress at scale
Always-on across every release
Platform & AI
Parallel cloud grid, every browser and device
One prompt drives 50 testing tools
Test assets and code export
Real user intelligence and analytics
Connect Jenkins, Jira, CI/CD
IBM, Coforge, Red Hat
Analyze End-To-End Tests
Platform & AI
Not three tools.
