Software Testing--work 1.5 understanding of software testing

Premise: Personal work and internet-related, so the summary content is biased in this respect, if there are other different suggestions or need to add, please leave a message to make bricks, communicate with each other, learn from each other!

First, what is software testing

Software testing is to minimize the human and material resources to ensure product quality of the process, do a pre-planning, do a good job in the middle process, feedback and problem solving.

Second, why the need for software testing

If there is no software testing, there is no guarantee that the product in the test process in accordance with specific requirements, and no one dedicated to the product function, logic and other special testing, can not guarantee the quality of the product release is very easy to have a major problem, especially in the case of large product user volume, Economic losses and corporate image losses are not predictable.

Third, the software testing work flow and test engineer's work content

The process of software testing mainly includes:

(1) Requirements Review

(2) test plan

(3) test plan

(4) The Division of specific functional modules, the determination of test points and the writing of test cases

(5) Specific test execution

(6) Bug follow-up and repair verification

(7) Make final version regression according to basic release standards, and complete the release

(8) After the product release, continue to follow up the problem of operation feedback, reproduce the scene, and assist to analyze and solve the problem of user scenario

Iv. classification of bugs in software testing process

(1) User experience--including interface design, process jump, etc.

(2) Functional--A logical error, a function that is not implemented, or a particular problem that occurs in a specific scenario

(3) Compatibility-including the compatibility of external environment (compatibility with other software), the compatibility of the internal environment (a large software installation directory of the old and new version of the file compatibility (such as a new +b old, a old +b new, etc.), and hardware and software compatibility (such as the hardware interface modified, Causing the software to be inaccessible)

(4) Performance--Hang the machine for a long time or a frequent operation, there is a memory leak, or high CPU consumption

(5) Abnormal situation--the design of the use case can be all of this part of the content to be extracted (such as testing the speed of the network, connected to the WiFi, or not directly connected to WiFi, etc.)

(6) Loading and unloading upgrade--new Ann loading and unloading, covering and loading, upgrading function

V. Design of test Cases

The design of the test case can be basically based on the classification of the bug, so that it can be more comprehensive coverage to:

(1) Functional (2) compatibility (3) performance (4) User experience

In addition, the design of test cases requires a distinction between smoke testing, detailed testing, and regression testing to design different test cases

The following is the experience of their usual record:

The focus here is on the client content (PC and Android)

Enter the page as an example, generally include the input box and the confirmation button

Functionality:
1, the input box any content is not entered, click the Confirm button (Note: Here must increase the sentence null logic, otherwise the program will throw an exception, resulting in a crash; other similar)
2, input box only enter a box, others do not input (and so on), click the Confirm button
3, input box input format error (including other characters not allowed to enter, with the input points, such as IP only input number, input length limit, special character limit), click the Confirm button
4, for the input box part can be entered, some optional cases, only input must be entered, click the Confirm button
5. Input box input the correct content and format, click the Confirm button (can set the correct success?) ）

Performance:
1, when the input content has a problem, click the confirmation button how long can give a response?
2, the input content is correct, how long can set the success, give the correct response?

Interaction:
1, input box display (main tab content), input box arrangement, and Confirm button layout, style consistent
2, the input box is correct, error prompt

Compatibility:
1. International environment Compatibility:
Compatibility of client products--different operating systems
If it's a web-side-focus on different browsers
If it's mobile--focus on different phone models, mobile phone systems

2, good-neighborly compatibility:
Compatibility with other software
Compatibility with a number of products that need to be safety-sensitive
Compatibility with a number of drive-level related products

3. Internal compatibility:
The compatibility between your own products-new and old files
Between your own product and your brother's products-compatibility of calls to each other (our products call DLLs for other products, etc.)
Compatibility issues during the release of updates-for example, after some modules have been upgraded, the old is still in memory and must be restarted by the main program of the product, so in this case it is necessary to load the old and load new and test the original program,
See if there is a problem

Vi. Summary of test methods

Mainly includes the following many, all for their usual summary:

1. Traditional test methods:
Focus on functions, logic, user experience, and other requirements, summarize test points, write test cases, test

2. Comparison test method:
This method is more appropriate to have the product call our DLL when used, determine the program flow, the old version of normal and abnormal place, modified to the new version, verify that the old version of the abnormal place to be modified, normal place is still normal

3. Analogy test method:
This method can also be called the migration test method, such as considering the download or upload encryption problem, in a project to learn this note, in other projects also need to pay attention to this point

4. General test Method:
Products related to security and to the privacy of the user itself must be encrypted and cannot be decrypted by the outside world; for some processes that require a permanent process or that may be permanent, you need to focus on performance tests (hanging too long will not collapse;
Whether the program will appear stuck or disorganized)

5, positive reverse combination test method: For example, the program Web side and the app side of the linkage corresponding test

6, tools and real-world comparison test:

7, test normal and abnormal situation all need to consider

Software Testing--work 1.5 understanding of software testing