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

Outline end-to-end test methodology, including hardware specs

Open
  • Is something wrong?
#253 1 comment 3 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
documentation

Research direction

Start by reviewing the methodology sections on the staged site, including the runtime page, and the existing Lighthouse tests via Puppeteer. Document the device, OS, display, CPU tuning, browser and server versions, isolation procedures, and relevant network and CPU-throttling caveats for each test run.

Written by the indexing model from the issue text.

Description

Hey folks,

I'm a huge fan of this effort, so thank you first and foremost for making this data legible.

Over on the staged site (https://framework-tracker.pages.dev/), the methodology sections (e.g.: https://framework-tracker.pages.dev/run-time/#:~:text=39.21ms-,Methodology,-Each%20framework%20renders) do not yet include enough information. For each test run, I would expect to see:

  • Device brand and specs (CPU, memory, disk, GPU (if discrete) and GPU rendering status)
  • OS version
  • Screen resolution(s)
  • A note about CPU core tuning (has anything been done to change default frequency scaling? If not, a line saying that)
  • Browser and server software versions
  • Other isolation procedures used to ensure that the workload is uninterrupted (e.g., via a link to a larger methodology document).

Given that we're also using Lighthouse tests via Puppeteer, it would also be helpful to make some of the caveats about the network and CPU throttling it can apply somewhat plain.

Dominant language
TypeScript
Stars
42
Forks
16
Avg merge
13h 28m
Merged PRs (30d)
149

Getting set up

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 e18e/framework-tracker

All issues in e18e/framework-tracker

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.