Skip to content

Define and publicise our standards for testing and CI gating #1019

@JamieSlome

Description

@JamieSlome

As part of our community meeting yesterday (19th May 2025), we agreed that a small overhaul of our testing approach is required. This thread came about as a result of PRs going stale that had already met test thresholds but had not been merged. We want to encourage a highly automated environment (where possible) to reduce burden on maintainers. Testing can provide assurance around new code, without a maintainer having to powerlift too much!

Wishlist ❇

  • Migrate tests from Mocha to Jest
  • Update docs site to include guidance and specification on how to test and level of coverage required
  • Discuss and conclude on minimum code coverage required for PRs and patches
  • Discuss and conclude on automatically merging PRs if all checks (including testing) have passed

(cc) @dave-gantenbein - let me know if I've missed anything and can update 🤗

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions