024.lv — automated QA platform for web control panels
Currently in development. 024.lv automates server control panel testing: it explores sections, detects interface and network issues, stores results, and produces clear HTML and JSON reports.
1 / 6
024.lv, also known as Berg Panel Tester, was created to solve a recurring operational problem: checking a large server control panel after every meaningful change. Reviewing dozens of screens by hand is slow, difficult to repeat consistently, and prone to missing a broken link, a browser error, or a page that never finishes loading. The platform turns that work into a structured quality assurance cycle.
The task
The tester had to sign in safely, move through the panel’s main modules and assess more than the HTTP status. It needed to verify what an operator actually sees across web hosting, databases, mail, DNS and networking, storage, system tools, SSH, security and administration. The output also had to serve two audiences: a readable review for the team and structured data suitable for the next development pass.
What was implemented
- Playwright browser flows with authentication and automatic session recovery.
- Navigation discovery that identifies panel sections not yet present in the test manifest.
- A ten-level check covering PHP and error pages, empty content, navigation, headings, performance, stalled loaders, JavaScript, network requests and interactive controls.
- Human-style interaction with scrolling, hover states, search input and broken-image detection.
- Semantic checks for tables, forms, badges, metrics, dates, tabs, pagination and API responses.
- MySQL storage for test sessions, page results, findings, console errors and failed network requests.
- Filterable HTML reports with charts, plus machine-readable JSON with priorities and practical fix guidance.
Architecture and control
The testing core is written in Python and uses Playwright for browser automation. MySQL keeps the history, Jinja2 and Chart.js build the detailed report, and a password-protected PHP dashboard provides a practical place to start a run, watch its progress and reopen previous results. Runs can be narrowed by module group or priority, launched in headless mode, or limited to discovering newly added sections.
The result
The team receives one view of test coverage, page status, issue severity and the exact context behind each finding. Saved report history makes changes visible over time and helps developers isolate regressions after a deployment without repeating the same manual inspection from scratch.
The project remains in active development: the core testing and reporting workflow is already in use, while scenarios and semantic checks continue to expand alongside the control panel.