A functional test of a Righthand all-day date versus overnight time
Test: Supply an all-day closure on Tuesday and a timed visit from Monday night to Tuesday morning.
An organizer wants a schedule result that keeps distinct event types.
This article is from Righthand. The test inputs and example result are illustrative. No test in this article has an executed result.
Prepare the test case
Supply an all-day closure on Tuesday and a timed visit from Monday night to Tuesday morning.
A Righthand has its own phone number and email address, with text, email, phone, and Slack communication. Introduction.
The initial test uses supplied information and the Righthand's own email. For direct account work, a separate available connection operation is necessary. Connections.
Give the task instructions
Read the supplied dates and event types.
>
Send the closure and timed visit independently.
>
Keep their end-date meanings explicit.
>
Send the owner the result in this conversation.
>
Use Pacific time for the supplied deadline.
Identify any permitted outward action explicitly. With Ask, the instruction or approval must identify its recipient and task. Connection tool permissions are another required control. Communications Policy.
Examine an illustrative result
Tuesday is the closure date. The visit starts Monday and ends Tuesday.
The organizer gives approval for the exact intended calendar representation.
The acceptance conditions
The result must keep the all-day date and overnight timed interval.
Compare the result with the original case information. Examine the teammate's received message when contact is part of the task. A send record and recipient-visible receipt are different observations.
Converting both into identical calendar dates fails the test.
If the result fails an acceptance condition, stop that responsibility at this scope. Examine Activity for questions, account problems, or the actual communication.
Give the missing source or owner decision before another attempt. If sending has an uncertain result, establish what occurred before repeating it.
Keep a small test record
Record the task instructions, source information, received result, and owner decision. Record the configured communication policy and applicable connection permissions.
Select the next task
A direct record, existing app function, or human teammate can be sufficient when no continuing conversation or coordination is necessary. A Righthand is an alternative when the owner wants responsibility for the next steps and decision handoff.