Secure Coding & Release Discipline ยท Lesson 4 of 4
Tests and review before release
Study notesAbout 3 minutes. A full lesson with quick checks is on its way.
In short
Outside a declared emergency, every fix needs its tests and a second pair of eyes before it ships, however sure you are.
In your work
You've fixed a payment bug for a client and you're confident it's right. Nothing tests it yet and no one has looked at it, so you add a test that reproduces the bug and ask a colleague to review it.
What the UK rules say
- The UK's Software Security Code of Practice expects a clear process for testing software and updates before they're released.
- The NCSC's secure development principles include continually testing your security, not just before launch.
What to do
- Write a test that fails before the fix and passes after it.
- Ask for review, explaining the change and its risk.
- Use the emergency process only when it's genuinely invoked, and follow up afterwards.
Watch out for
- Merging your own pull request because reviewers are busy.
- 'I'll add tests later', which rarely happens.
In your organisation
What is your organisation's emergency change process, and who can invoke it?
Your employer's own policies come first.
Sources
- GOV.UK (DSIT and NCSC), Software Security Code of Practice (opens in a new tab), checked 6 October 2026.
- NCSC, Secure development principles: continually test your security (opens in a new tab), checked 6 October 2026.
UK law and guidance, explained for learning. Not legal advice.
