Software testing experience

As a very important part in the software development process, software testing has become the focus of software developers and users. Perfect testing is the guarantee of software quality, so software testing has become an important and arduous task.

1. feature details
Before performing the test, you must first classify the functions to be tested and enter the test function breakdown table. Then, you can run the functional test cases to test each functional subdivision point one by one. Before each test case is run, the purpose and expected output results of this operation should be clarified and recorded.
2. Pay attention to errors in the test.
There are some errors that are closely related to the programming skills and habits of program developers. For example, misspelling or usage in a program. Collect and record these phenomena to help you discover similar errors more quickly.
3. Use as many unconventional tests as possible
All valid input and illegal input and various boundary conditions are fully taken into account. The boundary value is often the most prone to exceptions. In special circumstances, it is even necessary to create extreme states and unexpected states, such as sudden network interruptions and sudden power outages. The following situations are specific:

(1) Perform a boundary test to test the maximum number and minimum number of values in the user input box, and the case where the value is null.

(2) Illegal test. For example, enter a letter in the place where a number is entered.

(3) tracking and testing, tracking a data process, and ensuring data correctness.

(4) ensure data correctness before starting the test, and then identify various bugs from the system.

(5) during interface testing, programs are prone to errors in the interface. Do not take it lightly if you want to test this module.

(6) code reuse test. Some modules have almost the same functions during the development process. When reusing code, developers may forget to modify or modify the original code in an incomplete manner, resulting in errors.

(7) Emergency Testing, testing of unexpected conditions on the server, such as network interruptions, power outages, and other extreme situations.

(8) In external environment testing, some systems are dependent on another system during development, and the system is affected when an error occurs in another system.

(9) system compatibility testing. For example, some programs run normally in IE6 and cannot run in ie5. Some programs can run in Win2000, but cannot run in Win98.

(10) Users' ease-of-use tests often result in constant changes to users' needs. One of the reasons for changes is that users' operations are inconvenient.

4. There must be a validation process for the test error results.
Generally, there is a test error, and a B is required to confirm it.
5. develop strict test plans
The test schedule should be as loose as possible. Do not complete a high-level test in a very short time.
6. full attention must be paid to the relevance of regression testing.
After a developer fixes a bug, find another one. Often, the developer only fixes the reported defects and does not consider other features that may cause errors again when being modified. It is not uncommon to modify an error and cause more errors.
7. Test Documents should be as detailed as possible
The functional points in the test function breakdown table can be as detailed as possible. The input data, output data, error prompts, and testing time of each running test case can be recorded truthfully and in detail, the time when the test is completed to facilitate future backtracking of the test.
8. Emphasis on communication and communication
This includes communication with program developers, testers, online technical forums, and netizens, and communication with customers. If you think more, communicate more, ask more questions, and communicate with each other, you can avoid many detours and learn a lot at the same time.
9. Good at summing up
All problems and exceptions found during the testing process, common mistakes and valuable lessons learned by developers, the skills discovered or learned when using the system and operating the database, and the experiences gained when using the test tool can be recorded on the laptop or computer. These will be valuable materials that can be referenced in future work and will also become valuable experiences.
10. Properly save all test process documents
These test documents are used to facilitate the reproduction of tests, follow-up after the event, work backtracking, summarization, and reports.