How thecoolqateam/online-inspection-tracker works
Project Type and Purpose
• This project is a full-stack application built to perform automated UI inspections for web applications. The goal is to detect UI anomalies (such as page white screens and pixel deviations) and provide real‐time feedback with alert notifications via tools like DingTalk, Feishu, and WeChat.
• The README outlines features, deployment instructions, use cases, and an overall architecture that supports scheduled inspection tasks.
File Structure
• Notice the clear separation between the frontend and backend:
• The “online-client” directory contains a Vue3-based client (notice the presence of Vite config, App.vue, components, router, and stores). This handles the user interface, including dashboards for inspection records and data visualization.
• The “online-server” directory is a Spring Boot application written in Java, following an MVC-like structure (with controllers, services, mappers, entities, and configurations) to provide REST APIs and schedule test jobs.
• The “db” folder and Docker configurations (in the “docker” directory) indicate that a MySQL database is used, and the system is designed for containerized deployment.
• The repository also includes Dockerfiles for “mysql”, “server”, and “web”, making it clear that the system runs in containers for consistency with production deployments.
README for Additional Insights
• The README confirms that the frontend uses Vue3, while the backend uses Spring Boot along with testing tools like Playwright and TestNG.
• It also explains the scheduling (every 5 minutes) of the UI inspection tasks, the reporting of test results (visual and textual feedback), and supports integrations to messaging platforms for alerts.
• There are detailed deployment steps for local installation and Docker-based deployment, emphasizing distinct responsibilities across client, server, and database.
a. Main Components:
• Frontend (online-client): Vue3 application that provides the UI (inspection dashboards, test case management, data visualizations).
• Backend (online-server): Spring Boot application that exposes APIs, handles business logic, processes scheduled inspection tasks, and coordinates with test automation tools.
• Database: MySQL (setup using db/ddl.sql and containerized under docker/mysql) to persist test case information, test results, and configurations.
• Docker Containers: Three containerized services are evident from the “docker” directory — one each for the frontend web server, backend server (with the onlineInspect.jar), and the MySQL database.
b. Relationships and Interactions:
• The Vue3 frontend makes REST API calls to the Spring Boot backend.
• The backend communicates with the MySQL database for CRUD operations.
• The backend also integrates with third-party notification services, as indicated by utilities like DingUtil, FeishuUtil, and WechatUtil, to alert users about inspection results.
• Scheduled inspection tasks (triggered within the backend using jobs like TriggerUrlJob) may call Playwright for automated UI tests and interact with external sites (inspection targets).
c. Architectural Patterns and Design Principles:
• Separation of Concerns: The frontend and backend are completely decoupled.
• Containerization: Docker is used for consistent deployment across environments.
• MVC Structure: The backend’s directory structure (controllers, services, mappers, entities) points to an MVC pattern.
• Automated Scheduling and Real-time Feedback: The backend runs periodic inspection tasks and updates a UI dashboard on the frontend.
d. Relevant Technologies:
• Technologies such as Vue3, Vite, and related tooling for the frontend.
• Spring Boot, Java, Maven, MyBatis, TestNG, and Playwright in the backend.
• MySQL for data persistence.
• Docker for container orchestration, including separate Dockerfiles for each major component.