Testing

Choose tests around the behavior being changed:

• Use RPC tests for object behavior and HTTP integration tests for Worker routing and response contracts.
• Verify that one object retains state across calls and different object identities remain independent. Inspect SQLite state when persistence itself is the contract under test; repeated calls alone do not prove recovery after restart.
• For alarms, verify the scheduled work’s effects and any rescheduling or cancellation, using the documented helper to avoid waiting for wall-clock time.
• Check the installed integration’s isolation model before reusing object names. Use separate identities or explicit cleanup where state is shared between tests.

Keep package versions, imports, configuration, helper signatures, and runnable examples in the linked documentation rather than copying them into this reference.