Talking about software testing process

This week I have been on two software testing technology courses, can be said that the software testing technology has a macro concept, but the specific content or confused, so also take this opportunity to search for relevant content on the Internet, a cursory understanding of the software testing process, which will help me in the future of software testing technology learning, Let me briefly talk about my personal insights into the software testing process after learning by myself.

Many undergraduates who are not involved in the work know what software testing technology is, but they do not have a clue about the specific process. As a general rule , software testing begins when the project is established and is preceded by the following key links:

Requirement analysis → test plan → test design → test environment setup → test execution → Test record → defect management → software evaluation →RTM

Prior to the elaboration of the relevant issues, we first clarify the division of labor, in general, requirements analysis, test case writing, test environment construction, test execution, etc. belong to the test developer work category, and test execution and defect submission are common testers of the scope of work, the test leader responsible for the entire testing of all aspects of tracking, implementation, Management and so on.

The test flow is as follows:

Demand analysis

Demand Analysis (requirment analyzing) should be said to be an important part of software testing, how the test developer's understanding of this link will directly affect the next test work to be carried out. There may be some who think that testing needs analysis doesn't matter, and that's a bad idea. Demand analysis is not only important but also critical!

in general, requirements analysis includes software function requirement analysis, test environment requirement analysis, test resource requirement analysis and so on. One of the most basic is the software functional requirements analysis, testing a software first to know what the software can achieve what functions and how to achieve. For example, a Smartphone includes features such as VoIP,Wi-Fi , and Bluetooth . Then we should know how the software to achieve these functions, in order to achieve these features need to test equipment and how to set up the appropriate test environment, or else the test will not talk about!

since we are talking about demand analysis, what can we do to analyze it? You can't imagine it. to Be sure, testing requirements analysis is based on software requirements documentation, software specifications, and developer design documentation, and it is believed that companies that manage some specifications have these documents in the software development process.

Test Plan

test plan istypically written by a test lead. The test plan is based mainly on the project development Plan and test requirements analysis results. The test plan generally includes the following aspects:

1. Test Background

1. A. introduction of software projects;
2. B. the project involves personnel (such as hardware and software project leader, etc.) and corresponding contact information.

2. Test basis

1. A. software requirements documentation;
2. B. software specifications;
3. c. Software design documentation;
4. D. Other , such as reference products.

3. Test Resources

1. A. test equipment requirements;
2. B. test personnel requirements;
3. c. test the environmental requirements;
4. d. other.

4. Test Strategy

1. A. adopt test methods;
2. B. what test environment to build;
3. c. What testing tools are being taken to test management tools;
4. d. training of testers and so on.

5. Test Schedule

1. A. test requirements analysis;
2. B. test case preparation;
3. c. test implementation, according to the project plan, the test is divided into which test phase (such as unit testing, integration testing, system testing phase, α, beta test phase, etc.), the focus of each phase and input resources.

6. other.

The test plan also includes information such as the date and author of the test plan, and the more detailed the plan, the better. plans do not catch up with changes, a plan to do well, when practical implementation will find it often difficult to follow the original plan to carry out. such as the lack of resources in the software development process, personnel flow and so on will have a certain impact on the test. Therefore, these require the Test Manager to be able to control from the macro. In the face of change to be able to deal with the freedom, the chaos is not surprised that is the best.

Test design

The test design mainly includes the test case writing and the test scene design two aspects. A good test case is a good guide to testing and can find a lot of software problems. For test case writing, see the article "talking about test Cases", which is written in the previous section, which is described in detail. The test scenario design is primarily a test environment issue.

Test environment Setup

Different software products have different requirements for the test environment. Software products such as C /s and b/S architecture, then for different operating systems, such as Windows series,Unix,Linux and even Apple OS , these test environments are required. For some embedded software, such as mobile phone software, if we want to test the power consumption of the function module, cell phone standby time, and so on, then we may need to set up a corresponding current test environment. Of course, the test for the environment such as mobile phone network is required. The test environment is important, and the test environment that meets the requirements can help us accurately measure software problems and make correct judgments. to test a piece of software, we may use many different test environments depending on the point of demand. Some test environment we can build, some environment we could not build or build a high cost. In any case, our goal is to test software issues and ensure software quality. Test the environmental issues, or take the most economical approach based on the specific product and the developer's actual situation.

Test execution

The test execution process can also be divided into the following phases:

Unit test → integration Test → system Test → factory test, in which there are regression tests at each stage.

From the point of view of testing, test execution involves a quantity and degree of problems. That is, the scope of the test and the degree of testing. For example, what does a version need to test? To what extent should each aspect be tested?

From the management point of view, in a limited time, in the case of limited or even shortage, we should consider how to divide the division of labor, how to use resources reasonably to carry out the test. Of course, the following questions should also be considered:

1. what should be done when the tester does not perform in place and is perfunctory?

2. test efficiency, how to improve the efficiency of testing?

3. according to the different characteristics of the version is only to do verification tests or smoke test or complete system testing?

4. How do you deal with occasional random problems during the test?

5. What to do when there are many new problems in the version? Test Stop standard?

6. ...

In short, the test execution process will encounter a lot of complex problems, or that sentence, specific problems specific solution! This article does not do too much elaboration.

Test history

The defect record generally includes two aspects: who submits and the defect description. in general , the flaw is who tests who submits it, and of course some companies may, in order to ensure the quality of the defects submitted, will conduct a defect assessment prior to submission to ensure the accuracy of the defects submitted. the description of the defect should include at least some of the following elements:

Serial number

Title

Preset conditions

Operation Steps

Expected results

Actual results

Comments

Degree of severity

Probability

Version

Tested by

Test date

The above is the description of a bug is usually described in the content, of course, when the actual submission of the bug can be supplemented by actual situation, such as the attached piece,log file.

In addition, a version of the software testing, but also to test the situation of the test report, which is also a link to go through.

Defect Management

Defect management, many companies take the defect management tools to manage, common defect management tools have Test Director,bugfree and so on.

Software evaluation

The assessment here refers to the software that is prepared to be sent to the customer is evaluated to determine whether it can be issued to the customer or to the market after a round of tests have been conducted to verify that the software has no major problems or problems. the software assessment team is usually composed of the project leader, the marketing staff, the department manager, etc., or the third party personnel designated by the customer.

Test summary

Each version has a test summary of each version, each stage has a test summary of each stage, when the completion of the RTM project, generally to the whole project to do a review summary, see what to do the shortcomings of the place, what experience can be used for reference in the future test work, and so on. Test summary No strict format, word limit. It should be said that the test summary is always needed.

Test Maintenance

Due to the incomplete testing, when the software is officially released, the customer in the process of use, there are some problems, some even serious problems, which need to modify the relevant issues, after the revision of the software need to test, evaluation, distribution.

Talking about software testing process