Managing Scans
Browse, filter, re-run, share, and delete scans from the Website Scanner list.
Managing Scans
The Website Scanner list (/web-scanner) is the hub for every scan in your workspace.
The scan list
Each row shows:
- Scan name
- Status —
pending,running,completed, orfailed - Score (for completed scans)
- Total issues
- URLs scanned
- Created by
- Created at
- Shared-with-team badges (if applicable)
Screenshot (TODO): Scan list with filters, search, and row actions
Scope filters
Use the scope tabs at the top of the list:
- Mine — scans you created.
- All — every scan visible to you (your scans + any scan shared with an accessibility team you belong to).
Search and filter
- Search — free-text match on scan name.
- Status filter — narrow to pending / running / completed / failed.
- Date ranges — filter by created-at or updated-at windows.
- Team filter — show scans shared with specific accessibility teams.
- Sort — by name, score, total issues, status, or created date; ascending or descending.
Row actions
- Open report — click the scan name or the row.
- Re-scan — run a new scan with the same URLs, WCAG version, rule toggles, and auth config.
- Share with team — see Sharing scans.
- Delete — moves the scan to trash; report data is removed within the plan-tier retention window.
Trigger — manual vs scheduled
Every scan is either manual (you ran it yourself) or scheduled (the platform ran it automatically on a recurring cadence you configured).
| Trigger | What you see in the list | How to spot it |
|---|---|---|
manual | Standard scan row | No clock icon |
scheduled | Run number badge (Run #3 etc.) | Clock icon in the row, plus the parent schedule's recurrence label (e.g. "weekly") |
Configure a schedule when you create a scan — set scheduleConfig.enabled = true and pick daily / weekly / monthly, time-of-day, and timezone. TestKase queues the next run via QStash and creates a fresh child scan each time. Each child gets its own row in the list and increments the run number on the parent.
To pause: open the scan, edit, and toggle the schedule off. To stop entirely: delete the parent scan (children stay for retention).
Status lifecycle
pending → running → completed
↘ failed- pending — queued, not yet started.
- running — at least one URL is actively being scanned.
- completed — all URLs finished successfully; report is viewable.
- failed — one or more URLs could not be scanned. The row shows a message explaining why (most often: unreachable URL, auth failure, or rate limit). See Troubleshooting.
Pagination
The list paginates in batches. Large workspaces can scroll through hundreds of scans without loading every page at once.
Comparing and consolidating reports
Once you have more than one scan, two extra report views unlock:
- Compare — diff two runs of the same scheduled scan to verify a fix or track a regression.
- Consolidate — merge multiple independent scans into one combined report (with PDF export) for audits or executive review.
See Comparing & Consolidating Scans.