Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

test(playwright): probe playwright-cli attach --extension against a real signed-in Chrome on a local machine

Abierto
  • ¿Algo no está bien?
#6,475 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
playwright, shell
Área
documentation, testing

Línea de trabajo

Run the three probes as written: playwright-cli attach --extension=chrome from a Windows shell and from WSL2 against a signed-in Chrome with the Playwright extension installed, plus attach --cdp on a non-default profile with a debug port, recording command, OS/shell, Chrome version and exact error for each. Then read docs/adr/0056-verify-ui-with-linux-side-playwright-and-attach-produced-demo-evidence-to-prs.md (Open items and Alternatives considered) and context/e2e.md under testing:run-e2e to see where the result belongs: a rubric row for the logged-in-session case if a probe passes, otherwise an Alternatives-considered entry with the failure reason. The blocker is access to a local Windows machine with a signed-in Chrome profile — confirm you have that before starting, and check the linked issue comment for maintainer guidance.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

help wanted needs-triage priority: medium

Goal

Find out whether @playwright/cli 0.1.22's attach --extension (and attach --cdp) can drive the user's own signed-in Chrome on a local workstation, as a candidate for ADR 0056's "Needs a logged-in session" rubric row (now in testing:run-e2e context/e2e.md).

It cannot be tried from a cloud container: it needs a real Chrome profile with the Playwright browser extension installed, which only exists on a local machine.

What 0.1.22 documents

playwright-cli attach --help:

--cdp         connect to an existing browser via cdp endpoint url.
--extension   connect to browser extension, optionally specify browser name (e.g. --extension=chrome)
--session     session name (defaults to bound browser name or "default")
--idle-timeout  detach after this many milliseconds without a command. attached browsers are never detached by default.

Probes (run each and record pass/fail with the exact command and error)

  1. Windows shell, native Chrome: install the Playwright extension in the signed-in Chrome profile, run playwright-cli attach --extension=chrome, then goto a site the profile is signed in to, snapshot, and screenshot. Does it reuse the signed-in session? What consent prompt appears, and does it need a human click every time?
  2. WSL2 (NAT networking), same Windows Chrome: repeat probe 1 from WSL2. ADR 0056 notes Chrome 136+ ignores remote-debugging switches on the default profile, so --cdp to the default profile is expected to fail. Check whether --extension gets around that from WSL2.
  3. attach --cdp against a separate, non-default Chrome profile started with a debugging port (Windows shell, then WSL2 via the gateway IP). Record what works.

The former probe 4 (agent-browser on WSL2) is dropped: the 2026-10-07 benchmark found no reliability winner and agent-browser was not adopted, so it is no longer a candidate.

Done when

  • Each probe has a recorded result (command, OS/shell, Chrome version, outcome, error text).
  • If probe 1 or 2 passes, propose a rubric row for the logged-in-session case in testing:run-e2e (context/e2e.md) and an ADR 0056 note. If both fail, add them to ADR 0056 "Alternatives considered" with the reason.

Related

  • ADR 0056 (docs/adr/0056-verify-ui-with-linux-side-playwright-and-attach-produced-demo-evidence-to-prs.md), Open items: the Claude in Chrome from WSL live test needs the same machine and can run in the same sitting.
  • melodic-software/claude-code-plugins#6477 (the agent-browser vs playwright-cli benchmark, which deferred attach --extension and a Playwright MCP arm to this local probe).
Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
5 h 18 min
PR fusionados (30 d)
869

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.