4 ms·
> You claim that static code analysis has different responsibilities, but then you leave out what those responsibilities are. https://en.wikipedia.org/wiki/Sta
by rewmie 3y ago
> You claim that static code analysis has different responsibilities, but then you leave out what those responsibilities are.
https://en.wikipedia.org/wiki/Static_program_analysis https://en.wikipedia.org/wiki/Static_program_analysis
If you're interested in onboarding onto the topic, you can start by reading the first paragraph of the Rationale section.
- gavinhoward 3y agoI am well aware of what static program analysis, thank you very much. > The uses of the information obtained from the analysis vary from highlighting possible coding errors (e.g., the lint tool) to formal methods that mathematically prove properties about a given program (e.g., its behaviour matches that of its specification). Sounds like finding defects to me.
- pixl97 3y agoHow do you do runtime analysis on an application before it's ready to run?
- rewmie 3y ago> I am well aware of what static program analysis, thank you very much. You see, I don't think you are. If you were, you certainly wouldn't make totally oblivious claims such as "static analyzers are for when your test suite is subpar." > Sounds like finding defects to me. If you were familiar with static analysis tools, you'd be well aware that they only cover a narrow class of defects, which other classes of automated tests do. Again, I seriously recommend you onboard onto the basics of automated testing, specially the intro section on the classes of tests and what are their design goals, and in the meantime refrain from posting comments on testing.