Lint and test stages
Keep fast checks close to a change
Lesson 5 of 20 · 12 min · Module 2: Gates and build outputs
Cheap checks can catch obvious problems before more expensive build work.
Start this lesson →Free. No installation: you write and run the code in your browser, and it is checked automatically.
By the end, you’ll be able to…
- Separate the questions checks answer
- Give failures a recognizable name
The idea
A workflow combines an event boundary, job dependencies, and ordered steps. Conditions and prerequisite outcomes determine which jobs can run.
01Separate the questions checks answer
Lint can catch style and static problems; tests evaluate selected behavior. Neither proves every production scenario will work.
02Give failures a recognizable name
A named Lint step makes a failure easier to locate. Useful feedback includes what failed and which change it evaluated.
03Order work by cost and dependence
Run inexpensive checks before a build that relies on valid source. Keep the sequence understandable rather than merging everything into one opaque command.
Your turn
What the checks look for
- Runs lint before tests
- All checks pass in the model
Take this with you
Make checks both fast and understandable.
Go a little further
Describe which check you would run first for a syntax error and why.