Update Test Schema: Dev Server Startup
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #677 by @AlexanderKaran — merged
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start by reviewing PR #647 and the shared schema work in #633, then locate the development server startup test's schema, result generation, validation, persistence, and consumers. Check the main test records/schema for retained dependency snapshots before deciding how historical data can be migrated. Done when the test uses the shared base and concrete iteration schema, records the required identity and benchmark fields, and documents the historical data approach.
Written by the indexing model from the issue text.
Description
Update this test's schema to use the shared base or benchmark schema introduced in https://github.com/e18e/framework-tracker/pull/647.
Scope: development server startup time.
Use createBenchmarkBaseSchema with a concrete iteration schema, inheriting TestBaseSchema. Use MetricBaseSchema for each statistical measurement. Record runs and required iterations at the benchmark level.
Include the required test identity fields: name, framework, and packagePath. Update result generation, validation, persistence, and consumers as needed.
Where historical test data is available, convert past records to the new schema. Where the required data is unavailable, use the new schema going forward; do not invent missing measurements or iterations.
As a last resort, if the historical schema cannot reasonably be migrated, consider dropping affected past records or re-running the test using the dependency snapshots retained in the main test records/schema. Document the chosen approach.
Blocked by #647, the shared-schema part of #633.
Part of #633
- Dominant language
- TypeScript
- Stars
- 42
- Forks
- 16
- Avg merge
- 13h 28m
- Merged PRs (30d)
- 149
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from e18e/framework-tracker
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
e18e/framework-tracker#640 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 45/100
e18e/framework-tracker#666 ·
Maintainers usually reply within 1 day
-
Variance ChartsOpendocumentation
Difficulty 5/5 Over a week Newbie friendliness 35/100
e18e/framework-tracker#665 ·
Maintainers usually reply within 1 day
-
TanStack Bar ChartOpendocumentation
Difficulty 4/5 3-5 days Newbie friendliness 45/100
e18e/framework-tracker#664 ·
Maintainers usually reply within 1 day
-
TanStack Line ChartOpendocumentation
Difficulty 4/5 1-2 days Newbie friendliness 45/100
e18e/framework-tracker#663 ·
Maintainers usually reply within 1 day
All issues in e18e/framework-tracker
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
maniator/verticopolis#1303 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
components-web-app/docs#297 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
appwrite/mcp-for-docs#23 · 1 comment ·
-
`@vanilla-extract/turbopack-plugin`: "getImageSize is not a function" with Next.js 16.4.x when a `.css.ts` file imports an imagePossibly taken @aevarOrigo claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vanilla-extract-css/vanilla-extract#1799 · 1 comment ·
-
native
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
prime-radiant-inc/evener#4839 ·
Maintainers usually reply within 1 day