Automating fitness functions
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
run fitness functions continuously so the signal is cheap and early.
Planned topics
- Run in CI for structure (dependency rules, banned APIs, license and vulnerability checks).
- Run in pipelines or production telemetry for runtime qualities (latency, cost per order).
- Decide per rule whether failure blocks a merge, warns, or only reports a trend.
- Roll out gradually: record current violations as a baseline and forbid new ones.
Draft outline details
Demonstration
a CI job outline: build, dependency-rule test, vulnerability scan, then a nightly job that queries cost per order and posts a trend to the team channel.
Check your understanding
How can you adopt a strict rule on a codebase that already violates it?
Show answer
Baseline existing violations and fail only on new ones.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.