Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Closed Beginner friendly
  • Is something wrong?
#828 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, playwright
Domain
testing

Research direction

Start with tests/e2e/ and the existing Playwright specs, then run npx playwright test against a fresh npm run build:production. Add tests/e2e/docs-routes.spec.js for the three named routes, checking their articles, sidebars, content, links, and navigation targets. Done means the specified assertions pass and all three routes are covered without production changes.

Written by the indexing model from the issue text.

Description

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

Dominant language
JavaScript
Stars
0
Forks
2
Avg merge
13h 43m
Merged PRs (30d)
600

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.

More from cncf/endusers

All issues in cncf/endusers

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.