Testing is made up of two parts: "checking" and "testing" Checking that the system works according to specifications and implementation Testing to find bugs These two things together make a "good test".
Many of the bugs are "forgotten things" We want to do this Requir ement Specificat ion Design Implement ation Checking that it works as implemen ted Just to see if it works. Is that okay? ・Omission of requirement definition ・Discrepancies in understanding with higher-ups ・Leakage of specification ・Mistakes in design ・Failure to identify affected areas ・Discrepancies in understanding with PM ・Implementation errors ・Implementation omissions
If you can, actually touch the system while thinking, "How can I make this system have a problem?” about 10 minites. Then you may remember, "Oh, I forgot this!”