test-user-cleanup

To purge test users after automated testing, run a cleanup script that identifies and deletes accounts matching your configured pattern. The tool reads project.json for configuration and removes matching test data to restore a clean database environment.

Yes, you can run test data cleanup automatically in a CI pipeline. The tool supports manual, auto, and scheduled trigger modes, allowing it to automatically remove test user accounts after E2E test runs complete.

Test user cleanup enforces safety checks to block production data from being deleted. It uses pattern-based selection and age-based filtering to target only test accounts, ensuring real user data remains protected during the cleanup process.

To audit which test users will be deleted, run the cleanup tool in dry-run mode. Dry-run mode identifies and lists matching test accounts based on your configured patterns without actually deleting them, allowing you to verify the selection first.

The best way to remove test accounts created during E2E testing is using a dedicated cleanup tool with pattern-based selection. It targets only accounts matching your test patterns and supports scheduled triggers to maintain a clean database automatically.

Yes, you need to configure project.json to use automated test user cleanup. The tool reads project.json for cleanup configuration, including the patterns and filters needed to identify which test user accounts should be removed from the database.