The operational decision
Ensure a test cancellation changes the provider record and the caller-facing status consistently. A calendar integration should be evaluated as a sequence of actual operations, not as a connected badge. Availability, booking, changes and failure handling each need their own expected result.
Prepare the workflow
Use a synthetic appointment, inspect its final provider state and confirm that failed notification delivery does not change the underlying cancellation result.
Example wording for approval
“The example cancellation status comes from the verified calendar result. A notification delivery problem should be reported separately, without inventing a different appointment state.”
Worked example
A fictional cancellation succeeds in the calendar provider, but the email confirmation cannot be delivered. Record the appointment as canceled and the notification as failed; do not reverse one state to make the dashboard simpler. Staff can use the approved recovery process for the communication problem. A separate test makes the calendar action itself fail, which must leave cancellation unconfirmed. These cases help prevent a generic error banner from obscuring whether the meeting still exists.
Handoff record
Record these task-specific fields: appointment fixture, provider status, notification status, reviewer.
Acceptance check
Make the calendar action succeed while email delivery fails. The records should distinguish a canceled test meeting from an undelivered notification.
Legal intake capacity calculator ↗
Try Ava with your business’s public information ↗