From Functional Testing to Integrated Test Strategies: A Tester’s Growth Journey and Test Plan Design
The article shares a tester’s two‑year growth experience, illustrating how testing focus shifts from basic functional checks to comprehensive test plans that combine interface, data‑construction, mock, and debugging techniques for various backend, frontend, and full‑stack scenarios.
1. Newcomer Journey
When I first joined the B2C team, the workload was heavy and I mainly performed repetitive functional testing without time for test‑case design or project retrospection, which made it difficult to understand the business and craft effective test strategies.
In the C2B team I began using SCF interface testing and mock platforms, but initially applied them mechanically without clear efficiency gains.
2. Growth After Two Years
My testing focus evolved from merely verifying requirements to analyzing the entire lifecycle, identifying test points, and selecting appropriate methods for different project types.
Test methods also shifted: I now combine interface testing, log inspection, remote debugging, and data construction to improve coverage and speed.
3. Test Plan Design
Step 1: Deeply Understand Requirements – Clarify system functions and business processes to form a solid basis for test planning.
Step 2: Organize Test Points – List all functional points that need verification and expand them into detailed test cases.
Step 3: Choose Methods Based on Project Type
Full‑backend: use interface testing, log analysis, remote debugging, and SCF mock to validate automated product placement and pricing logic.
Front‑end‑focused: conduct functional testing on mobile devices, verify database state changes, and employ HTTP mock to simulate different front‑end scenarios.
Front‑back integration: map the entire process, use interface testing for state flow, data construction for complex scenarios, and code analysis for price‑difference calculations.
Example code used for price comparison:
// Communicate to get store‑clerk recycle price at 15%
if (employee.compareTo(inspector.add(employee.multiply(new BigDecimal(IMPUTATION_PRICE)))) < 0) {
return true;
}4. Conclusion
Testing has progressed from pure functional checks to a blend of interface and functional testing, from mechanical execution to designing tailored test cases for different project types, ultimately improving efficiency and quality.
转转QA
In the era of knowledge sharing, discover 转转QA from a new perspective.
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.