Skip to content
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.

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

Remove all Puppeteer references from the codebase #10241

Open
eduardoumpierre opened this issue Jan 24, 2025 · 0 comments · May be fixed by #10352
Open

Remove all Puppeteer references from the codebase #10241

eduardoumpierre opened this issue Jan 24, 2025 · 0 comments · May be fixed by #10352
Assignees
Labels
category: devops Features and tools supporting dev process. focus: fraud tools

Comments

@eduardoumpierre
Copy link
Contributor

eduardoumpierre commented Jan 24, 2025

Description

To complete the process of sunsetting Puppeteer, we need to remove all Puppeteer references from the codebase references to Puppeteer, including orphan code, and unused files and dependencies.

Acceptance criteria

  • The Puppeteer configuration files are removed
  • The Puppeteer dependencies are removed
  • Move all Playwright files from tests/e2e-pw to tests/e2e
  • Update all instances of tests/e2e-pw to tests/e2e in all files in the .github directory.
  • All tests and automated workflows should still run normally and pass.
@eduardoumpierre eduardoumpierre added the category: devops Features and tools supporting dev process. label Jan 24, 2025
@eduardoumpierre eduardoumpierre changed the title Remove all references of Puppeteer from the codebase Remove all Puppeteer references from the codebase Jan 24, 2025
@eduardoumpierre eduardoumpierre self-assigned this Feb 7, 2025
@eduardoumpierre eduardoumpierre linked a pull request Feb 11, 2025 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: devops Features and tools supporting dev process. focus: fraud tools
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants