test: remove default test watch from privacy center

[speaker-ender]

Description Of Changes

Quality of life change.
Aligns the privacy center test scripts so that the default test job only runs once.
A separate test:watch job is added for running tests with the watcher.

Code Changes

• No changes to actual code. Only package scripts updated.

Steps to Confirm

1. Run turbo run test and confirm that the script exits with pass/fail values
2. Run turbo run test:watch and confirm that all test suites re-run on changes

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ignored	Preview	Feb 23, 2026 7:07pm
fides-privacy-center	Ignored		Feb 23, 2026 7:07pm

[greptile-apps]

Greptile Overview

Summary

Aligned privacy center test scripts with other workspace conventions.

• Changed test script in clients/privacy-center/package.json from jest --watchAll to jest (run once)
• Added new test:watch script with jest --watchAll for continuous testing
• Added test:watch to root clients/package.json to enable turbo run test:watch across all workspaces
• Matches the pattern already established in admin-ui and fides-js workspaces

Confidence Score: 5/5

• This PR is completely safe to merge with zero risk
• This is a trivial quality-of-life change affecting only npm scripts. The changes align privacy-center with conventions already established in other workspaces (admin-ui and fides-js). No production code, dependencies, or configurations are modified - only developer-facing test runner commands.
• No files require special attention

Important Files Changed

File Analysis

Filename	Score	Overview
clients/privacy-center/package.json	5/5	Split test script into test (run once) and test:watch (with watcher), aligning with other workspaces
clients/package.json	5/5	Added test:watch script to enable watching tests across all workspaces via turbo

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Root as clients/package.json
    participant Turbo as Turbo
    participant PC as privacy-center/package.json
    participant Jest as Jest

    Note over Dev,Jest: Test (run once)
    Dev->>Root: npm run test
    Root->>Turbo: turbo run test
    Turbo->>PC: Execute test script
    PC->>Jest: jest
    Jest-->>Dev: Exit with pass/fail

    Note over Dev,Jest: Test Watch (continuous)
    Dev->>Root: npm run test:watch
    Root->>Turbo: turbo run test:watch
    Turbo->>PC: Execute test:watch script
    PC->>Jest: jest --watchAll
    Jest-->>Dev: Watch mode active

Loading

_{2 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}