Split up render-test page
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
Our current render test page is ~70MB in size gzipped. This means that it can take a while to download it from our Circle CI artifacts storage to inspect what failed.
A few ideas for how to change this:
- Split passed, ignored and failed tests into separate pages. We usually only care about the failed tests which should be only a small fraction of the test suite
- Link reference images directly to the repo instead of embedding them as base64 in the HTML page.
- Use lazy loading of images. This requires them to be separate files
- Split up test-suite by directory with an index page that links to individual pages
/cc @mapbox/gl-js
Contributor 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.
Research direction
Start by tracing how the render test page is generated and uploaded to Circle CI artifacts. Compare the proposed approaches—separate result pages, repository-linked reference images, lazy loading, or directory-based pages—and define completion as a substantially smaller artifact that still lets failures be inspected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100