"No exceptions" and software testing in the health check report

Some time ago, the company had a lot of health checks, such as CT and chest X-ray. The results of many column health checks on the Health Check table were "not abnormal". It was quite uncomfortable at the beginning. It was normal if it was normal, what is "no exception", but it is right to think about it carefully. Hospital wording is rigorous. The subline "no exception" is: No problem is found, but it does not necessarily mean no problem. This is why "Normal" is not directly entered. There are roughly two reasons for this analysis: (1) All truths are relative truths. The current medical knowledge cannot discover, explain, or guarantee that all problems are absolutely correct. (2) The subject of Operations and Analysis Based on theory is a person, different people increase the uncertainty of the conclusion due to technical skill levels and sense of responsibility. Therefore, "no exception" is a scientific statement.
So I thought of our software testing.
We all agree that software testing is "false proof" rather than "true proof ". That is to say, the purpose of software testing is to prove that the software has problems, that is, to find out the software problems, rather than saying that the software has no problems after testing. How close is the Health Check?
Why do I think so? Because there are some incorrect opinions in our development, these opinions hold that testing is the only means to ensure the quality of software; testing can identify all problems of software; testing is the responsibility of software quality; and so on. These ideas revealed that many colleagues have little knowledge about software testing and are not familiar with the software development process. With such a wrong understanding, many testers have taken the lead.
In fact, any part of the development process is responsible for Software defects. Each process of software production is critical to the quality of software. It is very simple. Food masters are not only skilled, but also demanding on raw materials. Everyone who has read "Grand changjin" knows that Han shanggong and changjin have been paying a lot for finding the ideal food for many times. The same is true for software quality. From the perspective of demand research, we should have a clear awareness of quality to reduce the chance of defect. Good Programming habits and good design ideas can also greatly improve code quality and software quality. Testing can only be done. This step cannot reduce Software defects because the defect generation process has ended, therefore, testing to reduce possible defects of the system is also a negative idea. Similar to health check, there is no test method to ensure that all system defects are identified, and the abilities and levels of different test teams are different, therefore, even if the tester says "we have tested and there is no problem", it does not mean that the software quality is OK, but at most it is "no exception "!