SLA deadlines
SLA due date test cases
A small set of deadline examples for checking business-hour, weekend, holiday, and timezone behavior before deadline logic ships.
SLA deadlines
Cases worth testing
- Start late in the business day and spill into the next working day.
- Cross a weekend and a Monday holiday in the same SLA window.
- Compare UTC input with a local business timezone such as America/Chicago.
- Add business days from a Friday and verify the result does not land on a weekend.
- Ask for next business day from a holiday and from a normal working day.
SLA deadlines
Common failure signs
- The due time lands outside configured business hours.
- Holiday-aware and holiday-unaware calculations return the same date for a known holiday case.
- The same request returns different results across systems because each one copied calendar logic differently.
- Batch item_id values are missing, so failed rows are hard to map back to tickets.
SLA deadlines
Named outputs to inspect
- For sla_due_at, inspect result.due_at with the expected timezone offset.
- For next_business_day, inspect result.date and confirm it is a working day.
- Check requested, succeeded, and failed counts before trusting any single row.
- Use RapidAPI after the checklist when you want managed auth and a playground.