liveBook · Manning

Comprehensive verification

As explained in Vibe Engineering

Verification that evaluates software across functional, invariant, performance, mutation, and security concerns.

Passing tests can still conceal serious risk: a feature may satisfy its happy path while failing under adversarial input, production load, or an integrating build system. section 1.6

Treat verification as several deliberate attempts to break the implementation:

  • Use property tests to probe invariants beyond expected examples. section 1.6
  • Use performance tests to validate service-level objectives and expose production-scale resource failures. section 1.6
  • Use mutation tests to prove that the test suite can detect meaningful defects. section 1.6
  • Derive security tests from a threat model rather than checking only whether the feature works. section 1.6

The missing attacker

Enrichlead had tests, but none were written by someone imagining an attacker; vulnerabilities therefore remained invisible during ordinary feature review. section 1.6

How Vibe Engineering covers it

How deep it goes
Extends testing from happy paths to invariants, SLOs, suite effectiveness, and threat-model-derived security, but does not specify tools.
Examples
Uses Enrichlead vulnerabilities, the Gemini CLI failure, and production-scale loop-over-records behavior as failure scenarios.
What you can do after
Diagnose weaknesses by applying property, performance, mutation, and threat-model-derived security tests.
How it connects
Connects property testing, mutation testing, performance testing, security testing, threat modeling, invariants, and service-level objectives.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.