# Choose checks for a change

Source: https://zotonic.com/docs/2983/choose-checks-for-a-change

URI: https://zotonic.com/id/2983

Language: en

Choose checks for a change.

Start with the behavior that could break. A pure helper needs focused input and result checks. A resource write also needs permission and persistence checks. A template change needs a rendered page with representative content.

Compile changed Erlang code before running tests. Run the smallest relevant test first, then checks for affected integrations. Use a disposable database for tests that write data.

Record what was checked and what was not. A successful compile does not verify a browser interaction, and a successful admin request does not verify anonymous access.

License: 

Attribution: 

Related resources: https://zotonic.com/api/agent/related/2983?language=en


## API access

- [API help](<https://zotonic.com/api-help>)
- [OpenAPI specification](<https://zotonic.com/openapi.json>)
- [This resource as JSON](<https://zotonic.com/api/agent/resource/2983?language=en>)
