What problem does it solve?
Verifying that the RDoc live-reload server (rdoc --server) works correctly after modifying server code, templates, generators, or routing requires repetitive manual checks of endpoints, caching behavior, and rendered pages.
Core Features & Use Cases
- Endpoint Verification: Runs curl checks against the root page, /__status JSON endpoint, class pages, CSS/JS assets, 404 handling, and path traversal protection.
- Live-Reload Validation: Confirms HTML pages embed the polling script and that touching a source file advances the last_change timestamp through the file watcher.
- Visual Testing: Uses Playwright CLI to capture screenshots of index and class pages for layout and styling review.
- Use Case: After editing RDoc's server routing or generator templates, run this workflow to confirm all endpoints return correct status codes and the live-reload mechanism detects source changes.
Quick Start
Start the RDoc server with bundle exec rdoc --server and run the endpoint and live-reload verification checks against localhost port 4000.