Introduction to Microsoft Software Testing

Introduction to Microsoft Software Testing

 

Microsoft's software testers are divided into two types: Test tool software development engineers and software test engineers. Test Tools software development engineers are mainly responsible for writing test tool code and testing the software using test tools; or developing test tools to serve software testing engineers. The software testing engineer is responsible for understanding the functional requirements of the product, testing the product, checking whether the software is correct, determining whether the software is stable, and writing corresponding test specifications and test cases. Within Microsoft, the ratio of Software testers to software developers is generally 1.5 ~ About 2.5, the practice of Microsoft software development has proved the rationality of this personnel structure. Microsoft believes that the tester's task is to identify problems in the product as much as possible from the user's perspective by constantly using and attacking the newly developed software products.

Microsoft mainly considers the following issues during the test: (1) All error possibilities should be taken into account in the test. At the same time, it is very strange to do something that is not done as usual. (2) In addition to vulnerabilities, the test should also consider performance issues to ensure that the software runs well and runs very fast without memory leakage, so that the software runs slowly. (3) software compatibility should be considered for testing.

The test documents used in Microsoft testing mainly include the following:

(1) the test plan is closely related to product development and consists of multiple components. All large-scale commercial software requires a complete test plan, each step required, and each part must comply with the specifications. Test Plan includes content: 1) Overview 2) test objectives and release standards 3) areas to be tested 4) Test Method description 5) test schedule 6) test resources 7) configuration scope and Test Tool

(2) Test Specification refers to the document written by each product field identified in the test plan to describe the testing requirements in the field. To compile a test specification, you must refer to the Product Specification written by the project manager and the development plan written by the developer. Each field should have a detailed test specification, so you need to refer to the test plan. Content of the Test Specification: 1) Background information 2) tested features 3) functional considerations 4) test considerations 5) test ideas

(3) Test Case test cases refer to documents describing how to test a certain field that meet the requirements described in the test specifications. Depending on the Test Specification (scenario) development, add test cases for new issues that are not taken into account based on test feedback. There is no fixed format for the test case. As long as the test steps and facts need to be verified are clearly indicated, any tester can complete the test according to the description of the test case.

(4) test report the test management personnel report the test results and discovered defects or errors to the entire product development department in the form of a test report. The purpose of writing a test report is to keep the entire product development department informed of the progress of product development so that defects or errors can be quickly repaired. The format of the test report is not fixed. It is required to fully and clearly reflect the current test progress. It should be easy to understand and avoid confusion or misunderstanding.

(5) Report defects or errors the tester reports the discovered defects or errors to the developer in the form of defects or errors. The purpose of writing a defect or error report is to repair the defect or error. The quality of writing a tester's defect or error report directly affects the developer's repair of the defect or error. Several key points should be covered in a defect or error report: 1) defect or error name 2) version of the tested software 3) priority and severity 4) step 5 of the report test) 6) expected operation result 7) Other information