Software testing Overview (1)

1. What is software testing?

In addition to the software product itself, the software testing objects also have product-related documents. software testing uses as little time and effort as possible to discover potential defects of software products as much as possible, prompting and assisting developers in locating and processing defects, to deliver a high-quality software product to the customer.

2. What is the purpose of software testing?

The purpose of software testing is to deliver high-quality products to customers. This product provides the functions defined in the requirement documents, performance requirements, and robustness, stability, and security requirements. in addition, software testing ensures the high quality of the software development process and reduces development costs.

3. What are the principles of software testing?

Start Software Testing as early as possible, and fully understand user requirements from the perspective of requirements.

Test the software from the user's perspective (act like a customer [ALAC]).

In terms of validity and objectivity, developers should be prevented from testing their own programs as much as possible, but developers are encouraged to conduct targeted debugging on their own programs.

Following the 80-20 rule, the test can only detect as many system defects as possible, but not all defects (in fact, some defects are discovered during long-term use ), generally, users spend 80% of their time using functional modules, accounting for only 20% of the total number of modules. 80% of defects occur in 20% of modules. when designing test cases, pay attention to the test focus.

Testing is a necessary condition for improving product quality.

After discovering Software defects, ask the developers to fix them. If there are any differences, submit them to the test Manager and the Project Manager will confirm them.

The consequences and risks should be notified in advance to determine the risks and responsibilities for the unreasonable requirements raised by the customer.

Strictly execute the test plan to avoid uncontrollable and repeated tests.

Analyze the test results carefully to avoid ignoring the exposed defects.

Properly Save the documents (test plan, test cases, test data, test results, and test analysis reports) generated during the test phase for future reference and regression testing comparison.