Tests
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.5k
- Forks
- 463
- PR merge metrics
- No merged PRs in 30d
Description
it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.
now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.
a lot of code can already be regression-tested by simply running all the demos and validating the .outerHTML of the dom, and diffing reference images of resulting uPlot canvases via something like https://github.com/mapbox/pixelmatch.
Contributor guide
No contributing guide indexed for this repository
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 with the repository's demos and determine how they can be run together without simulating interactions through Puppeteer. Define how each demo's .outerHTML and resulting uPlot canvas images will be captured, with pixelmatch considered for image comparison. Done means demo regressions are detected through DOM and reference-image validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data-visualization, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100