Merge branch 'main' into alyo2-remove-blueprints

Author: walteck

.github/workflows/markdown-check-links.json

@@ -1,5 +1,7 @@
 # Software Engineering Quality Framework
 
+> **Note:** Contributors must take all necessary precautions to ensure that sensitive data does not leak into Source Control Management Systems. You must ensure you have reviewed the [guidance on what to do should this happen](practices/guides/commit-purge.md).
+
 ## How to get started
 
 See the [Quick Start Guide](quickstart.md)

.github/workflows/markdown-check-links.yml

@@ -167,7 +167,11 @@ You may wish to score each individual component or system separately for these a
 #### 9. Testing
 
 - We have great test coverage.
-- Testing is everyone's responsibility.
+- Testing is everyone's responsibility and test is a first-class concern.
+- A failing test suite in CI gets immediate attention.
+- We support all team members to practice good testing, including by holding no-blame sessions to discuss any automation tests we should have added, and what we can learn from having missed them initially.
+- We build code for testability.
+- Tests (including both test code and test coverage & whether there are gaps) are part of our standard peer-review process.
 - Repetitive tests are automated.
 - Testing is considered before each work item is started and throughout its delivery.
 - We use the right mix of testing techniques including automated checks and exploratory testing.