> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incident.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Test incidents
> Run practice incidents without affecting your real data or notifying the whole company.
Sometimes you just want to practice without the whole company knowing, and without cluttering your incident library with fake data. Test incidents are built for exactly this.
Test incidents work almost exactly like normal incidents: you can set summaries, leads, escalate to others, create [workflows](http://app.incident.io/~/settings/workflows), and receive nudges.
The key differences are:
* They won't be announced in any announcement channels
* They won't appear in your dashboard or insights
* You won't be able to update your status page
* Workflows won't automatically run, but you can configure them to run on a case-by-case basis in the advanced settings within a workflow
**Our Statuspage integration is disabled in test incidents.** This is a safety measure to avoid updating public status pages when you're just trying the tool out.
### Creating a test incident
Type `/incident test` from any Slack channel to start a test incident.
If you need a fully isolated environment to test configuration changes, integrations, and workflows, consider setting
up a [sandbox environment](/admin/sandbox-environments) instead.