From Learning to Working: Reflections on a Software Testing Internship

From Learning to Working and Reflection

The author describes moving to Beijing, adapting to a new city, and starting a test‑internship within five days, noting the contrast between academic theory and real‑world testing where QA participates from requirement analysis to release.

What I Learned During the Internship

Common software used includes IDEA, MIT Kerberos Ticket Manager, Xshell, Charles/Fiddler/Whistle, Switchhost, Xmind, SourceTree, and Navicat for MySQL. Typical log levels (debug, info, warn, error) and their meanings are explained.

Key platforms mentioned are Beetle (code branch management), GitLab, TAPD (project management), a knowledge‑sharing platform, environment provisioning system, and an operations ticket system for account and VPN access.

Testing Environment

For iOS testing, the author outlines setting up Whistle proxy, ensuring the phone and computer share Wi‑Fi, installing certificates for HTTPS traffic, and disabling the proxy after testing.

Project Process

The QA role involves several critical nodes: requirement review with the PM, test‑case design (including equivalence class, boundary value, scenario, and error‑guessing techniques), case review meetings, execution of smoke tests, bug reporting in TAPD, and coverage checks on Beetle.

Key Participation Points

During requirement reviews, QA raises feasibility, completeness, and UX questions; test‑case design follows the structure of input data, preconditions, steps, and expected results; bugs are reported with clear, concise information.

Main Projects and Requirements

1. Search testing tool improvement – validating result differences between old and new search strategies and ES indexes. 2. Basic service interface testing – modifying hosts, initializing services, and writing simple interface test cases. 3. Billing 3.0 – creating and executing test cases for product, after‑sale, and withdrawal reconciliation, learning large‑scale project testing and issue localization.

Improvement Ideas

The author suggests deeper requirement familiarization, higher test‑case coverage, systematic bug triage (frontend vs. backend), better communication of issues, and a more structured testing workflow.