Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[quality] /resources, /community/governance and the platform-engineering TCG page have no end-to-end coverage

Chiusa Adatta ai principianti
  • Qualcosa non va?
#828 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
88/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
javascript, playwright
Ambito
testing

Direzione di ricerca

Inizia da tests/e2e/ e dalle specifiche Playwright esistenti, quindi esegui npx playwright test su un npm run build:production appena generato. Aggiungi tests/e2e/docs-routes.spec.js per le tre route indicate, verificando i relativi articoli, barre laterali, contenuti, link e destinazioni di navigazione. Il lavoro è completo quando le asserzioni specificate hanno esito positivo e tutte e tre le route sono coperte senza modifiche alla produzione.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

agent/quality hive/hosted-available-lke648397-260827-5n31 quality testing

Finding

Three routes that the site's own navbar and sidebars offer visitors are never
loaded by the end-to-end suite:

  • /resources
  • /community/governance
  • /community/technical-community-groups/platform-engineering

tests/e2e/ currently requests /resources/case-studies and
/resources/radar-reports but never the Resources landing page that links to
them, and no spec has ever requested either community doc (grep over
tests/e2e for those paths, main @ 7772dcf).

The source side is pinned — tests/docs-contract.test.mjs and
tests/root-docs-links.test.mjs assert frontmatter, slugs and that every
in-repo link target exists, and npm run test:unit:coverage reports 100% line
and region coverage for every src/ component involved. But those suites read
Markdown off disk; none of them can see whether the built site serves the
route. An MDX compile change, a sidebar_position clash or a theme regression
can leave a page reachable from the navbar while it renders an empty shell, and
CI stays green.

/resources is the highest-value of the three: it is the only doc on the site
whose body is hand-written JSX. It imports @docusaurus/Link and renders the
two pillar cards that are the sole entry points to the case-study and
radar-report tables. A <Link to> that stops resolving under the deployed
baseUrl breaks both entry points and nothing currently catches it.

Recommendation

Add one Playwright spec, tests/e2e/docs-routes.spec.js, covering exactly these
three routes:

  • /resources returns < 400, is not the "Page Not Found" page, renders its
    <article> and its nav.menu sidebar, and each pillar link ("Case Studies",
    "Radar Reports") navigates to the route it names and renders content there.
  • /community/governance renders its article and sidebar, still shows the
    "Source and license" admonition and the upstream cncf/tab link that the
    reproduced text may not be republished without.
  • /community/technical-community-groups/platform-engineering renders its
    heading and sidebar, and its relative ../governance.md link resolves to
    /community/governance at runtime rather than being emitted as a source path.

No production code changes; tests only.

Priority

  • Impact: medium
  • Effort: low

Coverage classification: unit-covered, not end-to-end-covered (priority 2).
Unit evidence: npm run test:unit:coverage @ 7772dcf. End-to-end evidence:
npx playwright test @ 7772dcf against a fresh npm run build:production —
113 tests, all green, none of them touching these three routes.

Filed by quality agent (hold-gated mode)

🐝 Hive Agent: quality | Instance: hosted-available-lke648397-260827-5n31 | SHA: 7772dcf

— hive: agent=quality backend=copilot model=claude-opus-5 copilot=1.0.88

Lingua principale
JavaScript
Stelle
0
Fork
2
Merge medio
1g 2h
PR unite (30g)
311

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cncf/endusers

Tutte le issue di cncf/endusers

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.