Building and Evolving a Static Check Framework for Unity Projects
This article describes how a game development team designed, implemented, and continuously improved a static checking framework for Unity assets and code, covering pre‑submission hooks, post‑submission scripts, daily checks, CI/CD integration, UI enhancements, and lessons learned for better quality assurance.
The team needed a reliable static checking system to ensure the quality of Unity assets and code. They started with two main parts: a pre‑submission check for art resources using SVN hook scripts, and a post‑submission check for scripts, design tables, and other resources.
Pre‑submission checks block uploads that do not meet defined rules, while post‑submission checks are triggered by the continuous delivery platform and run daily, sending results via IM bots, email, or automatically creating bug tickets.
To make the framework robust, they iterated through three stages: building the basic infrastructure, adding daily checks to catch missing references, and optimizing the UI to present errors clearly. Automation was achieved by invoking Python scripts from Windows scheduled tasks, calling C# interfaces, and uploading logs for analysis.
Key improvements included migrating the checks to a cloud‑based CDP platform for better performance and scalability, organizing scripts by folder structure, extracting common utility functions, and adopting object‑oriented design with a BaseCheck class for reuse.
They also emphasized the importance of user experience, clear error messages, and efficient follow‑up processes such as auto‑creating bug tickets and assigning them to the appropriate QA owners.
Overall, the framework evolved from a simple hook‑based validator to a comprehensive, maintainable system that enhances development efficiency and product quality.
NetEase LeiHuo Testing Center
LeiHuo Testing Center provides high-quality, efficient QA services, striving to become a leading testing team in China.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.