Tag

Testing

23 Thoughts filed under this subject.

  1. Testing the Go Port Against PHP
  2. Retire the Browser, Keep the Test Runner
  3. A Rewrite Can Change Data Without Changing the Price
  4. A PHP Test File Isn't One Migration Case
  5. Is Your Benchmark Doing New Work?
  6. The Order of Charges Changes the Price
  1. A Design Is Good for a Change, Not in Isolation
  2. A Characterization Test Is a Boundary, Not a Recording
  3. A Surviving Mutant Is a Question, Not a Score
  4. An Interface Does Not Make a Fake Substitutable
  5. A Mock Fortress Tests a Call Script
  1. Choose the Test Boundary from the Defect
  2. Coverage Tells You What Ran, Not What Your Tests Would Catch
  1. Construction Should Not Hide Durable Writes
  2. Global State Makes Local Reasoning Impossible
  3. Dependencies Should Be Visible at Construction
  1. A Rewrite Needs a Behavior Ledger
  2. A Characterization Test Is Not a Product Decision
  3. A Characterization Suite Is Scoped to a Change
  1. A Capability Interface Is Smaller Than a Vendor Client
  1. Test Cannot Prove Production When It Runs Different Rules
  2. Production Bugs Can Live in the Data, Not the Code
  3. Reproduce the Failure Before Repairing It