Skip to content

Clarification/context #163

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
iw-ezequiel wants to merge 6 commits into from
Closed

Clarification/context #163

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
79c33ba
Clarification/context
iw-ezequiel Aug 9, 2021
6a02d8b
Further definitions of green/amber
Aug 11, 2021
d4c7799
Clarification on usage and definitions
Aug 11, 2021
71486a6
Further definitions of amber/green
Aug 13, 2021
8177f44
Typos and tooling
Aug 13, 2021
e721203
Merge branch 'main' into green-amber-clarification
regularfry Feb 24, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion quality-checks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,8 @@ The checks are classified here based on the concerns they help to address:

## Usage

All applicable quality checks should be applied. Not all checks are universal, i.e. applicable in all contexts. For example, accessibility testing is only applicable to applications with a user interface.

All applicable quality checks should be applied. Not all checks are universal, i.e. applicable in all contexts. For example, accessibility testing is only applicable to applications with a user interface. The [Details](#details) section lists universal checks in black, and contextual checks in grey.d

The majority of these checks should be [automated](./patterns/automate-everything.md) via [continuous integration / continuous deployment](./practices/continuous-integration.md): the optimal sequencing of these checks within CI/CD pipelines will depend on the project's branching strategy, deployment strategy, etc.

Expand All @@ -32,6 +33,8 @@ We rate our applications against each of these checks as follows:
* Red = the quality check is not applied.
* N/A = the quality check is not applicable.

There may be further nuances to these definitions, and the sections detailing each check can expand considerably on the criteria as required. Everyone is encouraged to contribute to those, and discuss how they can be best be tailored.

## Tracking progress

We recommend tracking progress on an Engineering Quality dashboard, for example:
Expand Down
Loading