Which of the following is NOT a concern when using fuzzing to identify program faults?

Fuzz testing is a dynamic testing technique that involves providing invalid, unexpected, or random data as input to a computer program. The intention is to find vulnerabilities and bugs that could result in the application crashing or behaving unexpectedly. Understanding the characteristics of fuzz testing helps clarify that the statement about fuzz testing bugs often being severe reflects a valid concern rather than a non-concern.

The focus of fuzzing is indeed to uncover serious vulnerabilities that could lead to significant security issues, such as crashes, memory leaks, and exploitation vectors. Therefore, the assertion that fuzz testing bugs often indicate severe issues is correct and speaks to the effectiveness of the method in identifying critical flaws.

In contrast, the other options highlight genuine concerns about fuzz testing practices. For instance, it is known that fuzz testing can be time-consuming as it requires extensive setup and may involve running tests for extended periods to cover a range of inputs. Additionally, fuzz testers may not catch all minor bugs, as they typically focus on more severe issues that could lead to significant failures. Lastly, fuzz testing may only cover specific input scenarios, and therefore may not comprehensively examine all possible inputs a program might encounter, limiting the overall effectiveness of the testing approach.

Thus, the emphasis on severity in the context of fuzz