Internship Reflections on QA Testing Practices and Tool Adoption at ZhaiZhai

During a four‑month internship at ZhaiZhai, I, as a testing intern, experienced significant growth: from initial exploration of testing work to proficient use of various testing tools and platforms, while recognizing the importance of testing in the overall project lifecycle.

Project Practice and Growth

I participated in the quality‑inspection business testing work, learning professional skills and tools. Initially I only performed functional testing, packet capture, and database checks; now I use many testing tools and platforms to improve efficiency and quality. My understanding of the testing process and business has evolved from a superficial view to a comprehensive grasp of the workflow.

Testing Tools and Platforms

During the project I encountered several tools that changed my daily testing habits.

First, the case‑writing platform zzcase, a self‑developed case management system, uses mind‑maps for case creation, making the process more agile and organized. Its tagging feature (priority, smoke type, etc.) greatly improves case management efficiency.

Second, the Beetle platform provides code‑diff capability, which significantly improves testing efficiency and reduces missed bugs by allowing a clear view of code changes.

Third, the self‑developed apitest platform simplifies API testing compared to manual use of Postman or Whistle.

Additionally, a data construction platform dramatically speeds up data preparation, turning a complex pre‑process into a single click.

Other tools include various log‑viewing platforms and remote‑debug plugins, illustrating the principle “the tool shapes the work”.

Project Control in Testing

I gained a deeper understanding of the project execution flow, realizing that testers should participate early in requirement and design phases to improve overall quality, because catching bugs early reduces development cost.

Testing focus can be divided into three major stages:

QA Assistance Phase:

During the requirement stage, we ensure requirement quality by reviewing from both test and user perspectives, questioning design rationality, completeness, and usability.

Technical review meetings align product, development, and testing teams, helping testers understand flow, interfaces, and database design, and anticipate edge cases such as async, multithreading, or caching.

QA‑Led Testing Phase:

1. Test case preparation: Test cases are essential for team collaboration, covering diverse scenarios and preventing missed bugs.

2. Test case review: Summarize each case with a concise description, key details, and expected results to keep reviews focused.

3. Test execution: Record and communicate findings, reproduce bugs, perform deep analysis (packet capture, logs, debugging), and verify impact of code changes.

4. Post‑test activities: Continuous monitoring, issue tracking, and verification during acceptance, release, and gray‑scale stages.

Changes During the Process

Mindset shift: Learning to ask more questions early to improve efficiency.

Recognition shift: Understanding that quality is a team responsibility, not just testing tasks.

Attitude shift: Overcoming fear of complex problems by confronting them, turning curiosity into motivation.

Future Efforts

1. Strengthen full‑process project control ability, aiming to independently manage a large project from requirement to release.

2. Emphasize summary and reflection after each project to extract patterns and build personal methodology.

3. Improve coding skills beyond small Spring Boot projects, mastering enterprise‑level development frameworks and independent bug resolution.

Through these efforts I aim to become a more comprehensive and professional testing talent.

Finally, I am grateful to the ZhaiZhai QA team for their support and guidance.

About the Author

张晓娴，质检业务测试工程师

To learn more about ZhaiZhai's business practices, please follow the official WeChat public account below.