Unit 01 of 02
Quality Tools
Static analysis, code style checking, testing frameworks and the debugger — each as a tool that shows whether a behavior is seen inside or outside the run and whether it ships to production.
Published Updated
Lessons
- 01 Static Analysis Learn what tools that read code without running it can find, what they cannot, and how to measure whether a behavior reaches production with a single question. 2 min read
- 02 Code Style Checking Measure that unformatted code runs the same in both profiles, that only a style checker reports it, and where a formatter can change the meaning. 1 min read
- 03 Testing Frameworks Measure which profile an assert()-based check catches a failing assertion in, which profile lets everything pass, and why your own comparison helper works on both sides. 2 min read
- 04 The Debugger Measure which profile shows the information seen while debugging, that is, the argument value in the exception trace, the warning text, and the call stack, and whether it reaches production. 2 min read