processing / processing/p5.js-web-editor

CI: add coverage reporting, bump deprecated action versions

Open
#3,895 5 comments 0 reactions 1 assignee View on GitHub

@avinxshKD is already working on this.

Since Feb 24, 2026.

Enhancement
Dominant language
JavaScript
Stars
1.7k
Forks
1.7k
Avg merge
3d 4h
Merged PRs (30d)
8

Description

Increasing Access

First - there's no coverage tracking at all. No --coverage flag, no collectCoverage in the jest config, nothing. We've got ~55 test files and zero idea what they actually cover. Would be good to at least get text-summary output in CI so we have a number to look at. Doesn't need to be fancy, just run jest with --coverage and maybe set a low global threshold so it doesn't silently tank when someone guts a test file

Second - test.yml is still on actions/checkout@v2 and actions/setup-node@v1. Both have been deprecated for ages, they run on Node 12 internally, and GitHub's been spamming warnings in the action logs about it. Should be @v4 for both. Two-line change

Feature enhancement details

Neither of these is blocking anything, but it's low-hanging fruit and the coverage thing especially would be nice to have before more test work gets piled on.,.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.