Software Test first week study notes

Software Testing Learning Essays

WCX the first week of the Software test study notes

Start with the method of software testing, summarized as follows

Summary of the methods of software testing:

Test name	Test content
Black box test	The software system is treated as a "black box", and the internal structure and knowledge of the system cannot be understood or used. Design tests from the behavior of the software, not the internal structure.
White box test	The designer can see the internal structure of the software system and use the internal knowledge of the software to guide the selection of test data and methods.
Gray box. Grey Box test	Between the black box and the white box

is manual or automatic and can be classified

Test name	Test content
Manual Test Manual Testing	Testers use mouse to manually test (test GUI)
Automation Automated Testing	Program test program (Test API)

Classification from the purpose of the test

Test name	Test content
Unit Test Units Testing	Verify the accuracy of the program on the lowest function/parameter, such as testing the correctness of a function (developers do)
Functional Test Function testing	Verify the functionality of the module (testers do)
Integration Test Integration Testing	Verify the functionality of several interdependent modules (testers do)
Scenario Test Scenario Testing	Verify that several modules are able to complete a user scenario (testers do)
System Test Systems Testing	Tests for the entire system function (testers do)
Alpha Test	Software Testers perform thorough testing of the software in real user environments (testers do)
Beta Test	Real user testing in a real user environment , also called beta (end user)

The software testing process is :

The first step: Analyze the Products / projects to be tested , determine the test strategy, and develop a test plan. The plan was approved and turned to the second step. It is important to determine the correct test strategy and guidelines before starting the test work, which is the basis for the later work. It is only through the analysis of the test objectives and requirements that we can determine the input of the test resources.

Step Two: Design the test case. Design test cases should be based on test requirements and test strategy, the progress of low pressure, should be designed in detail, if the progress, cost pressure is large, you should ensure that the test case coverage to critical testing requirements. The use case was approved and turned to step three.

Step three: If you meet the startup criteria (entrycriteria), perform the test. Testing is performed primarily by building a test environment and executing test cases. Carry out progress control and project coordination during the test.

Fourth step: Submit the defect. This is done with defect audits and validation.

Fifth step: Eliminate software defects. Typically, the development manager needs to audit the defect and distribute the defect. The programmer modifies the defect that he is responsible for. After the programmer has completed the modification, go to the regression test phase. If the completion criteria (exitcriteria) is met, the test ends normally.

Sixth step: Write the test report. Analyze the test, summarize the experience and lessons, and change it in the next work.

Software test process management, mainly including software testing is what kind of process, how to evaluate a software testing process, how to perform configuration management and test risk analysis and test cost management.

Learn about the content summary of software testing, including:

The main work of software testing is validation (verification) and confirmation (validation), and the following concepts are given below:

Validation (verification) is a series of activities that ensure that the software correctly implements certain functions, that is, to ensure that the software does this in the correct way (do it right)

1. determine whether a product at a given stage in the software life cycle meets the requirements established in the previous phase.

2. the form of procedural correctness, that is, the use of formal theory to prove that the procedure is in accordance with the provisions of the design statute.

3. Review, Review, test, inspection, audit and other activities, or to certain processing, services or documents, such as whether the requirements and requirements of the consistent determination and reporting.

Confirmation (validation) is a series of activities and processes intended to verify the logic correctness of the software in a given external environment. That is to make sure that the software does what you expect. (do the rightthing)

1. static confirmation, not the actual execution of the program on the computer, through manual or program analysis to prove the correctness of the software.

2. dynamic Confirmation, through the execution of the program analysis, testing the dynamic behavior of the program to confirm the existence of software problems.

Software testing is not just a program test, software testing should include the entire software development period produced by the various stages of the document, such as requirements Specification, summary design documents, detailed design documents, of course, the main object of software testing is the source program.

Software Test first week study notes