| Scenario | What to verify |
|---|---|
| Custom REST endpoint | Route appears under /wp-json/almightysupport/v1, methods map correctly, signed-out users receive expected denial, staff receive expected success. |
| Ticket lifecycle automation | New ticket, email-imported ticket, chatbot ticket, reply, close, reopen, assignment change, department change, and spam path all behave as expected. |
| Frontend data extension | Data appears only for authorized users and does not break the frontend when absent. |
| Admin config panel | Menu appears, fields save, validation errors show, unsaved-change warning remains usable. |
| Email queue modification | Queued message still sends, failures are visible, and retry behavior remains safe. |
| Email-piping filter | Allowed senders, blocked senders, spam quarantine, replies, and new ticket import all remain idempotent. |
| Privacy extension | Exports include extension data and erasure removes or redacts extension-owned personal data. |
| Pro-gated behavior | Feature stays inactive when Pro is unavailable or license is invalid. |
Suggested local checks:
wp plugin list | grep -i awedesk
wp cron event list | grep alsp
wp option list --search=alsp_* --fields=option_name,autoload
curl -s https://example.test/wp-json/almightysupport/v1/tickets