[Work Note II] test work summary

In recent weeks, two projects have been followed, specifically a project and a mission.

First, the interface test

The task content is about the interface, this time on the interface test has a new understanding, by the way feeling that the past is too stupid. Previous Test interface, research and development will tell me how to test, see what kind of return value even if the test is finished, so the previous Test interface is very fast. The previous period of time to organize the document, found that there is a boss of the test case for the interface test, look in to know that I measured the interface is how rough ah.

Summarize the interface test:

1. The interface test is also to write test cases.

2. In the test case, specify the interface address, each parameter type and meaning, the type of the return value, and the meaning of each field in the return value.

3. Each parameter in the interface to write a test case separately, the use case should be set different parameter values, parameter values to cover the overall, here you can use equivalence class and non-equivalence class to divide the set parameter values.

Second, the test workflow of browser testing

The project content is the browser app. Before the boss in charge of the project test, I just follow the boss told me to do some tests. By three, the boss had more things to do with this project alone. Research and development over there has also been replaced by a newly graduated research and development. Starting from the four period, we finally began to formally recognize the position of the test.

Specific development process:

1. Product first give us (two research and development and I) a requirement document, we look first, after reading, together to the demand, clear what this issue to do, everyone talk about their own ideas, some problems in the implementation and so on.

2. The second day of the project, the main discussion of task decomposition, assessment of time, together to discuss a specific function of the implementation of the method, estimate the workload and time, test the corresponding assessment of the test time, and finally summarize the project development cycle. After the project requirements freeze, upload to SVN.

3. Research and development began to write code, test here began to write test cases.

4. After writing the test case, review the test case. Project team together, I put my test case about once, they are based on the use case to raise some of their own questions, say some of the land to be modified, after the discussion, I made corresponding changes to the use case. After reviewing use cases, use cases are frozen and uploaded to SVN.

5. After each function is completed, the test can begin to be tested, and the tester begins to test the corresponding function according to the use case. Enter the integration testing phase.

6. After the integration test is complete, you can return to the test. This is the time to test the overall logic of the software.

7. All crashes and must solve the bug after the validation is no problem, the overall test once again no problem can be sent online Mail Online.

8. After the line to do online regression testing and installation, upgrade test, these confirmed that no problem, this period can be ended.

Third, Reading

Read a book today to see a saying: "80% of software defects often live in the software 20% of the space." "This sentence has not been fully understood, but also to the work of sentiment."

Also see the book said research and development and testing like a mixer in the water and soil, stirring to equals when the quality is achieved, then, I would like to ask, is the product mixer?

The main impression is that.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

[Work Note II] test work summary