Software testing process and bug lifecycle?

To determine the type of bug, you need to have a deep understanding of the project (or product). This division is more important for the statistics of problem types.

Classification method 1: functional problems, design defects, interface optimization, performance problems, configuration related, installation and deployment, security related, standard specifications, test scripts, documentation errors, compatibility problems, user experience, and others.

Classification method 2: function, performance, interface, usability, compatibility, and others.

After finding the bug, then, it is necessary to distinguish the level of the bug, so that the developer can deal with the bug according to the priority of the bug, give priority to solving the urgent, fatal bug, secondary solve the serious bug, then solve the general bug, then solve the minor bug, and finally, solve the small problems on the interface, so as to improve the progress of software development and improve the quality of the software.

Test process: requirement analysis, test plan, test case, test execution, analysis results, test documentation.

Bug lifecycle: new, open, fixed, re-open, delay, reject, and closed

Process: Requirements analysis, test points, test plan writing, test case writing, testing, defect recording, regression testing, judgment test completion, test report submission, operation manual.

Lifecycle: New, Open, Modified, Rejected, Reopened, Deferred, Closed.

Software testing process.

Requirements analysis, test plan writing, test plan review, test case writing, test case review, unit test, integration test, test environment building, system test, user acceptance test.

Bug lifecycle.

Discover Open.

Repair. Shut down.

Software testing process.

Unit tests - > integration tests - > system tests - > confirmation tests, and many more.

Status of the bug:

New, Open, Pending Verification, Resolve, Close.

Draw a V model and you will understand: the left is the development process, which corresponds to the testing process on the right, the development is top-down, and the testing is bottom-up.

Development Process Testing process.

Feasibility study and acceptance test.

Requirements analysis system testing.

High-level design Integration testing.

Detailed design of unit tests.

Software coding phase.

1. The requirements analysis stage corresponds to the generation of requirements specifications, corresponding to the test generation of system test schemes, that is, prepared for system testing, this stage has completed the unit test and integration test, mainly to test the function and non-function of the software product, almost no test, so the test method is mainly black box;

2. The outline design stage corresponds to the generation of outline design specifications, and the corresponding test generates an integrated test scheme, and the unit test has been completed in this stage, which is a test that assembles each functional module, so it is also called assembly test. It mainly depends on whether the module call is normal, whether the interface is available, whether the data transmission is correct, etc., so the test methods used are almost white-box methods, such as path coverage, conditional combination coverage, etc.;

3. The detailed design stage corresponds to the generation of detailed design specifications, corresponding to the test generation of unit test schemes, this stage is the first test stage after the developer coding, which is to test the developed individual modules to ensure that the function of each functional module is normal, and the pile module and the driver module can be built to use, and the method is also based on the white box.

4. The criterion of white-box testing is to cover the internal logical structure of the program as much as possible, and the black-box is to cover all input and output interfaces as much as possible, including some static tests such as documents. In addition to the commonly used testing methods, a wide range of random tests need to be supplemented to achieve 100% coverage as much as possible.

If you have any questions, we can communicate, I hope it will help you! ~

You can go to the Internet to check the V-shaped structure in the software, the corresponding test of each stage is written very clearly, and I recommend a book "Software Testing Methods and Techniques" by Tsinghua University Press, which is quite comprehensive.

01 What software testing is and why it's important.

Software testing is really going through the whole software life cycle, because from the beginning of you, you need to understand how to test it, and then how to test it later? Then the results of the test are improved.

Software lifecycle: The life cycle of software from generation to end-of-life.

First, the project manager completes the requirements document through communication with the customer, and the developer and tester jointly complete the review of the requirements document, including the areas where the requirements are unclear and where there may be obvious conflicts or unachievable functions. The project manager completes the project plan by synthesizing input from developers, testers, and customers.

Then SQA goes into the project and starts counting and tracking.

Second, the developer completes the requirements analysis document according to the requirements document, and the tester conducts a review, and the main content of the review includes whether there are omissions or differences in understanding between the two parties. The tester completes the test plan document, which is described above what the test plan includes.

Third, the tester starts to write the test case according to the modified requirements analysis document, and the developer completes the outline design document and the detailed design document. These two documents serve as supplementary materials for testers to write test cases.

Fourth, after the test case is completed, the test and development need to be reviewed.

Fifth, testers build an environment.

Sixth, the developer submits the first version, and there may be unfinished features that need to be explained. Testers test and submit bugs to Bugzilla.

The seventh is to develop and submit the second version, including bug fixes and adding some features, and testers will test them.

8. Repeat the above work, generally after 3-4 versions, the number of bugs will be reduced to meet the requirements of shipment.

The ninth is that if there is a problem with customer feedback, testers are needed to assist in reproduction and regression testing.

In traditional bugzilla, the bug description should include the following information: and the software version corresponding to the bug; interface personnel for development; the priority of the bug; the severity of the bug; The module to which the bug may belong, if it cannot be confirmed, can be judged by the developer; The title of the bug, which needs to clearly describe the phenomenon; Bug description, you need to give the steps to re-bug as much as possible; Bug attachments can be used to provide relevant logs and screenshots.

A high-quality bug record is a bug record that is easy to understand, so it has high requirements for description, and can provide a lot of accurate information, which is a good help for developers to locate.

Our company has been using DayClear for software testing bugs. Rishiqing is a simple and easy-to-use software test management, which can reasonably allow employees to plan the software testing work schedule, so that managers can timely grasp the work saturation of test employees, the progress of software testing work, etc. This makes it easy for individuals to get the job done efficiently or as a team.

The core functions of Dayshiqing are schedule management, task collaboration, and work notes, which are organically combined with each other to make the work experience easier.

Objectives of test evaluation 1, quantify the test process 2, generate a summary report of defects and test coverage Problems of test evaluation 1, the test coverage is not used as the basis for reporting the test process, so that it is not known whether the test is over; 2. There is no defect assessment, which is an important indicator to measure the feasibility of the software; 3. Data entry tasks and corresponding evaluation activities are not carried out using special software tools, which makes these tasks burdensome and tiring. Test Coverage Criteria for evaluating how much testing is done Defect assessment An important indicator for evaluating software quality, usually evaluating the model assumes that the discovery of defects is Poisson distributed; A rigorous defect assessment examines the length of time between defects found during testing. The evaluation estimates the current reliability of the software and how the reliability of the software will improve as testing continues.

SQA Suite provides four forms of defect assessment: 1. The defect distribution report can generate a function of the number of defects and defect attributes. Such as testing requirements and status.

2. The defect trend report can see the trend of defect growth and decrease; 3. The defect age report shows the length of time a defect has been in a certain state 4. The test result progress report shows the execution results of the test process in several versions of the application under test and the test cycle. Step 1: Review the test diary 2, Evaluate the coverage of test requirements 3, Analyze defects 4, Decide if the criteria for completing the test are met, if the criteria are not met 1, Retest 2, Lower the standard 3, Determine a subset of the software that meets the criteria to see if it can be released.