Skip to main content

Execution Cleanup

The Execution Cleanup feature allows you to delete old test executions from the database to maintain system performance and manage storage efficiently.

Overview​

Over time, test executions can accumulate and consume significant database storage. The cleanup feature provides a convenient way to remove old execution records while preserving the integrity of your test suite.

Accessing the Cleanup Feature​

  1. Navigate to the Test Executions overview page
  2. Click the Cleanup button with the sweep icon in the top right corner of the page
  3. The Cleanup Configuration dialog will appear

Configuration Options​

The cleanup feature offers flexible time range options:

Predefined Time Ranges​

  • Last 30 days: Delete all executions older than 30 days
  • Last 90 days: Delete all executions older than 90 days (approximately 3 months)
  • Last 365 days: Delete all executions older than 365 days (approximately 1 year)

Custom Date Selection​

  • Custom date: Select a specific cutoff date using the date picker
    • Only dates in the past can be selected
    • All executions older than the selected date will be deleted

Cleanup Process​

  1. Select time range: Choose one of the predefined ranges or select a custom date
  2. Review selection: The date picker shows the selected cutoff date
  3. Confirm deletion: Click the "Delete" button
  4. Final confirmation: A warning dialog appears showing the exact date
  5. Execute cleanup: Confirm to permanently delete the executions
warning

The cleanup operation cannot be undone. All executions older than the specified date will be permanently removed from the database.

What Gets Deleted​

The cleanup operation removes:

  • Test execution records from the database
  • Associated execution metadata (status, duration, timestamps)
  • Test step execution details
  • Execution logs and results

What Remains​

The cleanup operation does not delete:

  • Test case definitions
  • Test step definitions
  • Storage artifacts (videos, screenshots) in S3/Azure/File storage
Storage Artifacts

Videos and screenshots are managed separately through storage-specific deletion policies. This means:

  • Storage files may exist without corresponding execution records
  • The application handles missing media files gracefully
  • If a video or screenshot is not available, a placeholder message is shown