Description
Provide a lightweight web interface for consulting test results without installing ModuleTester. This allows stakeholders (project managers, QA leads, clients) to review test plans and results from a browser.
Current behavior
- Results can only be viewed in the desktop GUI or as exported static files (HTML/DOCX).
- Sharing results requires exporting and sending files manually.
Expected behavior
- A simple web server (
moduletester serve) that serves test plans and results.
- Read-only interface: browse test plans, view results, filter by status.
- No test execution from the web (security concern) — execution stays on the desktop app.
- Shareable URLs for specific test plans or campaigns.
- Mobile-friendly responsive design.
Implementation ideas
- Use FastAPI or Flask for a minimal backend.
- Serve pre-rendered HTML from campaign data (JSON/SQLite).
- Simple Jinja2 templates with a clean CSS framework (e.g., PicoCSS, Bootstrap).
moduletester serve --port 8080 --data .moduletester/campaigns/.
- Optional: static site generation mode for hosting on GitHub Pages.
Acceptance criteria
Description
Provide a lightweight web interface for consulting test results without installing ModuleTester. This allows stakeholders (project managers, QA leads, clients) to review test plans and results from a browser.
Current behavior
Expected behavior
moduletester serve) that serves test plans and results.Implementation ideas
moduletester serve --port 8080 --data .moduletester/campaigns/.Acceptance criteria
moduletester servecommand starts a local web server