Tests are not repetitive work without brains. Test and development, like the brain, then hands.
Refuse to move bricks, pay attention to technology;
Grasp the needs, the ultimate experience;
To control the progress, efficient communication;
Testing technology
If you only work overtime, go miles, it's just a postman.
- Test the program "good": understand the software business process accurately, use the mature test framework and design method to ensure the testing coverage
- Test the program "bad": black box divergence, gray box analysis, white box detection, use all feasible ways and means to find the combination of conditions that could lead to program anomalies
- The program is "full": the overall balance between the correctness of the evaluation: compatibility, stability, performance, conflict. Targeted construction scenarios, design solutions, tools and scripting assistance to achieve the goal of evaluation
- Never complacent: Do not limit your ability to the specified platform, the specified technology, the specified test type, do not do in the comfort zone of the so-called "experts"
- Expanding knowledge boundaries: self-driven continuous learning, ability to independently launch test technology research, and research results
Computer
The nature of the test object is the code, not the test that can stand in the implementation layer to unfold, is imperfect
- Transparent understanding of operating systems, network principles, databases and data structures
- Understand Web products accurately, master the basic framework of Web services, understand server/client business logic and features
- Ability to accurately analyze and understand the way the program objects are implemented from the business logic level
- Self-driven scripting code, using a variety of scripts, tools, and constantly improve the efficiency of testing
Requirements analysis and user experience
User experience is not just a product manager, but a test engineer is the first user of the product.
- Accurately understand product objectives and analyze the rationality of demand design
- With large software system/platform needs to deconstruct the ability to effectively carry out the experience and evaluation of products not online
- Seamlessly switch between engineers and ordinary users, feel the product experience, propose improvements, and drive product improvements
Manage Progress
Progress control is part of the QA process and a qualified test engineer knows how to be responsible for the progress
- Based on test plan, work plan is developed independently, time is reasonable and efficiency is emphasized.
- Independent landing mission, reasonable advance, control progress, anticipate risks, actively respond to and solve problems
- Effectively improve collaboration with product and development teams through the necessary normalization
- Understanding cooperation, cooperation and efficient cooperation
Efficient communication
Communication throughout the testing process, efficient and quality communication, is the necessary skills
- Learn to change positions
- Learn to Smile
- Learn to listen
- Learn to Praise
The basic accomplishment of a qualified QA
