This is a mid-size Salesforce org. Every line is something a change can break.
- Each circle is an object — bigger means more relationships, up to 10. The biggest are the ones most code depends on.
- Green carries an Apex trigger — 20 of 39. Code runs when the record changes.
- A thin line is a lookup (50).
- A heavier line is master-detail (9). Deleting the parent deletes the child.
Point atTap any object to see what a change to it would touch.
How confident are you that your last change did not break something three objects away?
How long do you wait for a sandbox to find out?
Can every developer on your team test at the same time?
Fidelic.
It boots that org on your laptop in seconds. Your tests run against it the way they run against a real org, and every request can tell you exactly what fired. No sandbox, no queue, no shared data.
A real NPSP trigger ran before the record saved.
You saved a record. This is what ran.
Every save, update, and delete comes back with a trace like this. Which triggers ran, what each one changed, in what order.
DIB_CloseOnInsert is a bug we planted so you can see how it looks. The row two above it is where it flipped the status from Open to Closed. Paste your own trace
Everything on this page comes from a command you can run. See the receipts