Testing
Practical verification steps for product changes and docs changes.
by @saifyxpro
Product verification
Common checks for HeadlessX:
Also verify changed flows directly:
- API routes with
curl - SSE flows in the dashboard or terminal
- queue-backed jobs when Redis and the worker are involved
- YouTube flows when
YT_ENGINE_URLis configured
Docs verification
For the docs site:
If docs navigation or content changed, also verify:
- sidebar order
- pager links
- landing page docs links
- docs search/vector index freshness
Manual test expectations
There is no substitute for checking real states:
- loading
- empty
- success
- error
When a change affects setup or operations, test the instructions as written rather than assuming they still work.