processing / processing/p5.js-web-editor

Add End-to-End Testing with Playwright to Improve Stability and Accessibility

Open
#3,677 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area:Accessibility Feature Request Needs Discussion
Dominant language
JavaScript
Stars
1.7k
Forks
1.7k
Avg merge
3d 4h
Merged PRs (30d)
8

Description

Increasing Access

Ensures people with disabilities have access. Automated tests confirm the editor works with assistive technologies – screen readers in particular – proving our pledge to access exists in reality.

For new contributors. The test suite functions as a safety net for contributing to the editor, which makes it relatively safe for people with little experience of open source to contribute.

Ensures consistency for novices. Through automated testing and bug catching, this project builds stability and reliability in the editor - an important element the Access Statement singles out as an aspect of the tool being accessible to learners.

Feature request details

I propose we adopt Playwright to create automated tests that simulate real user interactions from start to finish. These tests would be integrated into the GitHub Actions workflow to run automatically on every pull request. which will will us

  • Instantly confirm that criticial /important features are working.
    
  • Block code changes that causes bugs etc.
    
  • Saving maintainers time in reviewing and mergin the Pull requests 
    

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.

Research direction

Start by reviewing the GitHub Actions workflow and the editor's existing test setup. Identify the critical end-to-end user flows and accessibility interactions to cover with Playwright, then define the pull-request checks and confirm they run successfully in GitHub Actions.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, javascript, playwright
Domain
accessibility, ci-cd, testing-qa, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.