liveBook · Manning

Risk

As explained in Build High Value Software Systems

The possibility of harm or loss, assessed here through the probability and impact of a failure and the time it remains undetected.

Risk is the possibility of harm or loss. In software delivery, assess it by considering a failure’s likelihood and impact, and how long a defect may remain undetected. Late detection lets correction costs grow, so safeguards should reduce risk without adding needless friction. section 2.3.4 section 5.3

Use risk to decide where testing should contain defects:

  • Use unit tests for business rules, calculations, and invariants. section 5.3
  • Use integration tests for boundary behavior such as persistence, API contracts, and authentication. section 5.3
  • Reserve end-to-end tests for critical user journeys; they are more expensive and fragile. section 5.3

Different failures, different exposure

A broken logging formatter may inconvenience a developer; broken authentication can lock out customers, while a faulty payment calculation can lose money. Their different impacts call for different testing priorities. section 5.3

Table 5.1 Activity ratio analysis of a simple workflow
System area
Risk assessment
First line testing layer
What should it protect?
User login/Authentication
High impact, medium likelihood
Integration
Correct authentication outcome and session handling
Database retrieval/Queries
Medium impact, high likelihood
Integration
Correct boundary behavior and data mapping
Business calculations logic
High likelihood, high financial impact
Unit
Deterministic correctness of rules and edge cases
Critical user journey (Login → Retrieve → Calculate)
High impact, low likelihood
Small, stable set of E2E
End-to-end customer-visible behavior
Logging/Formatting utilities
Low impact, high likelihood
Minimal, if any.
Core invariant only, avoid overtesting

Compare failure likelihood and impact with the suggested first-line test layer and the behavior it should protect. section 5.3

How Build High Value Software Systems covers it

How deep it goes
Maps defect containment across unit, integration, end-to-end, and production detection using impact and time undetected.
Examples
Contrasts logging, authentication, and payment failures, and maps login, retrieval, calculations, and user journeys to test layers.
What you can do after
Evaluate safeguards and test placement by weighing failure likelihood, impact, and how long defects may go undetected.
How it connects
Connects risk to software testing, defect containment, rework, and necessary non-value-adding work.

Also explained in

Compare how 13 books explain risk →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.