Protecting your systems during testing
Set how hard agents may push, which actions they must never take, and keep testing away from real users.
Each asset has its own safety settings. Agents receive them with every job, and researchers review findings against them.
Intensity
| Setting | Requests per second | Use it for |
|---|---|---|
| Gentle | Up to 2 | Fragile or shared production systems. |
| Standard | Up to 10 | Most staging and production apps. This is the default. |
| Intense | Up to 40 | Dedicated test environments that can take load. |
Limits
Turn a limit on to forbid that kind of action on the asset.
- Never delete or overwrite data
- Never email or text real users
- Never create payments or refunds
Good practice
- Test against staging when it mirrors production closely enough to answer your question.
- Use dedicated test accounts and test data, never a real customer's account.
- Tell your Zaaf contact about paths that are out of scope, testing windows and anything agents should know. Zaaf adds them to the asset for you.