1. Preface:
To do software testing, you must first understand what software testing is. The classic definition of software testing is: operating a program under specified conditions to find program errors, measure software quality, and whether it can meet Design requirements for the evaluation process.
In testing work, as a pursuing software tester, you must have your own principles:
First of all, there is a plan to carry out the test work as soon as possible, without self-testing, and trace back to the pursuit of users. The design and execution of the test should be separated.
The second is that there is no thorough test. As a tester, we must also be clear: high-quality software is developed, not tested. What is our pursuit? Of course, it is to find defects that have not been discovered so far. Is the object of software testing only "programs"?
The test objects should include software programs, documents and data. The purpose of software testing is to find various defects in the software, and testing can only prove that the software has defects, but cannot prove that the software does not have defects. Testing can reduce the defects in the software to a certain extent, rather than completely eliminate them. Testing is to find various errors and defects in the software with less use cases, time and manpower to ensure the quality of the software.
2. Body:
In this process, we cannot carry out endless testing and work to find out all the defects in the software. This is unrealistic and impossible. When time is urgent, how should we choose the priority of testing? Considered from the following aspects:
1. What are the features of the software?
2. Which functions are most commonly used by users?
3. If software modules can be sold separately, which modules are the most valuable?
4. Which function errors will cause user dissatisfaction and even compensation?
5. Which programs are the most complicated and error-prone?
6. Which procedures are relatively independent and should be tested in advance?
7. Which procedures are most likely to spread errors?
8. Which programs are the performance bottlenecks of the whole system?
9. Which programs do developers have the least confidence in?
To sum up, users are most concerned about, the most profitable, and the most error-prone. Considering these aspects, we can easily distinguish the priority of testing and start testing. How can we perform efficient testing?
There are a few suggestions: continuous integration means, start activities as early as possible, automated testing, and repeated testing. In addition, the 2-8 principle also exists in the testing work, that is, 80% of the software defects may exist in 20% of the modules. Any work has a process, and software testing is no exception. In software testing, there are unit testing, integration testing, system testing, and user acceptance testing in the testing phase. Unit testing and integration testing are generally done by developers, system testing is done by company testers, and user acceptance testing is to demonstrate system functions to users on the spot, which is usually done by testers and users. Regression testing is when the tester finds a software defect and submits it, and the developer makes the modification, and the tester performs the test again. In addition, we also need to understand the smoke test and regression test. The smoke test is a verification test of a basic function point. After the test of this basic function point is passed, the subsequent test plan will continue. Regression testing is after software error correction, design modification and software upgrade, it mainly conducts validity test and system test for the software modification and affected parts.
3. Summary:
Testing starts with requirements and starts with requirements reviews. How to carry out effective requirements reviews? There are two points: the review organizer sends the requirements document to the relevant reviewers for pre-review before the review meeting is held, and collects the pre-review comments before the formal review begins; reviews the issues at the review meeting to make the review more adequate and effective. There are many people participating in the requirements review, so what is the necessity for testers to participate in the requirements review? Fully understand the requirements to lay the foundation for subsequent test case writing; based on the understanding of the details of the requirements, you can more accurately evaluate the main points and workload of the test; find the ambiguities in the requirements and prevent the occurrence of defects.
I recommend a software testing exchange group, QQ: 642830685. The group will update software testing resources, test interview questions, and test industry information from time to time. You can actively exchange technologies in the group, and there are teachers who will answer related technologies for you. problem. Interested friends, hurry up and join the group to communicate and discuss.
