summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@kernel.org>2023-07-25 09:55:34 -0700
committerPaul E. McKenney <paulmck@kernel.org>2023-07-25 09:55:34 -0700
commit9dd539b079e908256ba0ec843c683804216747b2 (patch)
tree07559880963aefe05eb87ec1a2094b1454b23d57
parent0639550f571618158c768f2d5c6d229ad20f0ee9 (diff)
downloadperfbook-9dd539b079e908256ba0ec843c683804216747b2.tar.gz
debugging: Testing and static analysis as automated code review
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
-rw-r--r--debugging/debugging.tex8
1 files changed, 7 insertions, 1 deletions
diff --git a/debugging/debugging.tex b/debugging/debugging.tex
index 3916f659..d721b7f0 100644
--- a/debugging/debugging.tex
+++ b/debugging/debugging.tex
@@ -828,7 +828,13 @@ describe more sophisticated forms of static analysis.
Code review is a special case of static analysis with human beings doing
the analysis.
-This section covers inspection, walkthroughs, and self-inspection.
+Human beings are of course subject to inattention, fatigue, and errors,
+which underscores the importance of static analysis and testing.
+Done properly, these two activities can automate at least some aspects
+of code review.
+However, it does not appear that testing and static analysis will be able
+to completely replace manual review any time soon.
+This section therefore covers inspection, walkthroughs, and self-inspection.
\subsection{Inspection}
\label{sec:debugging:Inspection}