[Feature]: Built-in Method to Mask Sensitive Input in Test Reports

Open
#38,673 6 comments 17 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@dgozman is already working on this.

Since Jan 5, 2026.

Assessment

This issue has not been assessed yet.

Description

milestone
🚀 Feature Request
// Current implementation
await page.getByPlaceholder('Password').fill(process.env.USER_PASSWORD);
// Report shows: Fill "actualPasswordValue123"

The sensitive value appears in:

HTML test reports
Trace viewer
Console logs
CI/CD artifacts

**Current Workaround:**

// Manual masking using evaluate
await passwordField.evaluate((el, val) => {
  el.value = val;
  el.dispatchEvent(new Event('input', { bubbles: true }));
}, secretValue);

**Proposed Solution**
Add a built-in method or option to mask sensitive input values in reports.

Option 1: New method fillSensitive()

await page.getByPlaceholder('Password').fillSensitive(process.env.USER_PASSWORD);
// Report shows: Fill "********" or Fill "[REDACTED]"

Option 2: Add mask option to existing fill() method

await page.getByPlaceholder('Password').fill(process.env.USER_PASSWORD, { mask: true });
// Report shows: Fill "********"

### Example

```typescript
// Login test with sensitive credentials
async login(username: string, password: string) {
  await this.usernameField.fill(username);

  // Current: Password visible in reports
  await this.passwordField.fill(password);

  // Proposed: Password masked in reports
  await this.passwordField.fillSensitive(password);
  // OR
  await this.passwordField.fill(password, { mask: true });
}

### Motivation

**Security Compliance**: Prevents accidental exposure of credentials in test artifacts that may be shared with stakeholders or stored in version control.
**Developer Experience:** Provides a simple, intuitive API without requiring custom workarounds.
**Industry Standard**: Similar to how many frameworks handle sensitive data logging.
**Real-world Impact:** Affects teams testing authentication flows, API integrations, payment systems, and any application using environment variables for secrets.
This feature would significantly improve security posture for teams using Playwright in enterprise environments where test reports are reviewed by security auditors or shared across teams.
Dominant language
TypeScript
Stars
100k
Forks
6.9k
Avg merge
16h 8m
Merged PRs (30d)
281

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/playwright

All issues in microsoft/playwright

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.