The operational decision
Replace a connected badge with evidence that the intended operation works. 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 test calendar, inspect the actual appointment record and confirm the staff owner can see it; do not use a production matter as the fixture.
Example wording for approval
“This example calendar test creates a fictional meeting only. The connection is ready for the agreed scope only after the expected record and staff view are verified.”
Worked example
A supplier signs into a fictional calendar account and shows a connected status. Now request one synthetic slot, inspect the created event and ask the assigned staff reviewer to find it from their normal view. Then exercise a rejected write. These steps reveal whether the connection supports the actual promised operation and failure path. Keep test records clearly marked and separate from real consultations. A connection badge by itself proves neither booking visibility nor reliable scheduling behavior.
Handoff record
Record these task-specific fields: test calendar, operation, returned record, reviewer.
Acceptance check
Show a successful sign-in but a failed calendar write. The test should remain failed even though the account displays as connected.
Legal intake capacity calculator ↗
Try Ava with your business’s public information ↗