Recognize the value of software testing the software testing capability

What kind of software testing is what I want. Or, what is the value of software testing?

Everyone knows what the purpose of software testing is to improve the quality of software, so finding out the bugs in the software has become a concern (naturally ), the number of Bugs has gradually become a standard for measuring software testing engineers. Diagnosis and fixing have become a matter for developers.

If the software tester finds bugs without thinking about the bugs, the efficiency of software testing may be reduced. Because testers may bypass a bug or submit repeated bugs. The same bug may exist in multiple forms.

If testers submit bugs for development, the efficiency of developers may be reduced. It takes time for developers to reproduce bugs, analyze bugs, and fix them.

If the tester can diagnose and analyze the cause of the Bug based on the current test environment, it makes sense from the development perspective and test perspective, problems discovered can be solved in a timely manner. On the other hand, the quality of software is far better than the above methods.

This is why I want to discover the problem and diagnose it. It's cool for me to come.

XX Project test process, summary:

1. Developers track the entire process

This method greatly reduces the time for developers to reproduce bugs and establish software testing environments.

When the project is not tight, the effect of such full-Process Tracking in the initial stage is still obvious.

When the project is tight, you need to control the depth (involving the depth ).

2. Gradually go deep into the tested project architecture and implementation

Only when you know and know each other can you be defeated. As a test engineer, you must be able to discover bugs and diagnose and analyze bugs. This diagnostic analysis capability is based on understanding the project. Only when development and testing work together can the problem be solved in a short period of time. Sometimes (Some people) may be in different positions and cannot obtain the effective information of the Project, which leads to errors during execution. How can this problem be solved? First of all, you need to know that the network is really a good product. All the things you can think of and think of may be obtained through it. You have existing resources for the project to be tested, is the keyword. The other is to communicate with the persons involved in the project under test. Resources can be shared to make progress together. Don't be stingy