Tests are not flat.

Many test engineers emphasize the testing methods and ideas. What are the testing methods and ideas?

The idea of testing is a three-dimensional approach. Physics often uses "animals living on the sphere" to visually illustrate the differences between two-dimensional space and three-dimensional space when talking about multi-dimensional space, here I also want to use the concept of multi-dimensional space to talk about testing.

In my opinion, the test should have at least three dimensions:

• Test level-- Software testing is carried out at different levels, such as unit testing, integration testing, and system testing. Unit testing is the lowest level. The testing object is the smallest unit of the software system. The integration test object is the intermediate level. The testing object is a subsystem composed of multiple units; the system test is a high-level test, and the test object is a complete system.

• Test Type-- Test types and test levels are orthogonal dimensions. Test types refer to different types of tests performed on test objects, the same type of tests can be reflected in different levels of tests. For example, performance tests may be conducted in unit and system tests, but in these two tests, performance tests are also reflected in different ways-performance tests in unit tests focus on the evaluation of unit performance.AlgorithmPerformance evaluation, while performance testing in system testing focuses on user experience. Performance Testing results reflect the overall performance evaluation of the system.

• Testing Background-- The focus of testing is another dimension. Simply put, it is to consider the design of testing from the perspective of who it is. For example, the function test is to check whether the function points are complete one by one from the perspective of "system implementation", while the user scenario test is from the perspective of "user, check that the system business processes or operation scenarios that users are most concerned about can be smoothly implemented.

The world of testing is three-dimensional and multidimensional, which means that testing engineers must analyze the problems from multiple perspectives. From the perspective of thinking, we should try to verify the correctness of the system and the possibility of discovering problems from multiple aspects.

As for the test method, the pointer is used to divide the test based on some standard or comparative standard methods, in this way, a relatively small test set can be used to overwrite the input space of the system as much as possible. Common black box testing methods, equivalence classification, boundary value analysis, and State Migration charts are typical testing methods.

Extend this question-we talked about the ideas and methods of testing and their differences. What is the significance of this for testing engineers? I think the discussion here is most suitable for answering a frequently asked question "What skills should test engineers have ?", My answer is:

1. From the perspective of the test method, the test engineer must master the test design method;
2. It is far from enough to grasp the test design method. There is also a need to have corresponding testing ideas;
3. Starting from the test idea, the test engineer should at least understand the differences between different levels and the focus of each level of the test. The test type should be mastered to understand the focus of each type of test, differences and overlaps. You need to master the background knowledge of the system (also known as business knowledge) and understand the structure of the system, focus on system testing from the perspective of the system itself and users.