Submissions by KentBeck

Expand to Extract and Back

Test Desiderata 12/12: Tests should be inspiring

Test Desiderata 11/12: tests should predict production

My Memories of Larry Tesler, Parent of GUIs and Slayer of Modes

Tests Should be Specific [video]

Test Desiderata 9/12: compose the results of tests to reduce the cost of testing

Test Desiderata 8/12: Tests should be isolated from each other [video]

Test Desiderata 7/12: Automated. Warning, this is mostly a design issue

Tests should be deterministic, with a goofy Gusto counter-example

Outcome Over Output: Also Impact and Effort

Output over outcome: 1/2 (with memoji)

Test Desiderata 4/12 tests should be easy to write

Test Desiderata 3/12 tests should be written to be read

Latency/throughput tradeoffs, illustrated with coffee

Test Desiderata 1/12: tests should be sensitive to behavior [video]

Decisions, Decisions or Why Baskets of Options Dominate

Publishing on Medium, with the stats they don't make obvious

Fast and Slow in 3X: Explore/Expand/Extract

Software Test Desiderata

Understanding legacy code with TCR (test && commit || revert)

3X: Explore/Expand/Extract at Facebook

Software design is also about relationships

Curiosity as a Service – Literally

“Testing” software design. A short feedback loop for design

Software Design is Human Relationships: Waiters, Changers, and Sufficiency

Development requires behavior and structure changes, setting up human conflict

To simplify review, have diffs change behavior or structure but not both

Narrowing an Interface in Tiny Steps

Buy Effort and Sell Value