End-to-end acceptance testing
Use an administrator account, make a current backup before structural changes, and never paste passwords or complete API or licence keys into screenshots or support requests.
What this guide covers
- Where to find every control used in this workflow
- What each setting changes and when to use it
- How to verify the result before relying on it in production
- What evidence to collect if the result differs from the expected behaviour
1. Test account and licensing
Prove purchase, account, download, activation, update and deactivation.
Procedure
- Complete a test order.
- Open My Products and copy the matching key.
- Activate on a staging site.
- Download/update.
- Deactivate and confirm capacity returns.
The entire entitlement lifecycle is self-service.
2. Test Assistant
Use private sessions and representative catalogue/site questions.
Procedure
- Test known and unknown questions.
- Test comparison, variations, cart and contact.
- Test mobile/accessibility.
- Review logs, cost and retention.
Answers are grounded and actions safe.
3. Test Publisher
Use one controlled topic through research, draft, approval, scheduling and publication.
Procedure
- Verify providers and Search Console.
- Review sources, images, links and SEO.
- Test cron and a deliberate provider failure.
- Verify sitemap/canonical and rollback.
Automation is predictable and observable.
Final verification
- Save the configuration and reload the screen to confirm it persisted.
- Test in a private browser session so administrator state and old cookies do not hide the real visitor experience.
- Test one normal case, one boundary case and one deliberate failure.
- Review the relevant product log, job, report or diagnostic screen.
- Record the installed product, WordPress, PHP and WooCommerce versions with the test result.
Troubleshooting checklist
- Confirm the licence is active for this exact product and environment.
- Check provider access, billing and model availability.
- Clear every active cache layer after settings or content changes.
- Verify background processing and inspect the first error, not only the final symptom.
When to contact support
Contact support only after repeating the test with caches cleared and current versions. Include exact steps, expected and actual results, the safe error text and a diagnostic export when available. Mask licence and API keys; do not send customer personal data.