[To Do] Add visual regression (Backstop) tests to Less
Open
Nobody has claimed this yet.
good first issue
low priority
up-for-grabs
- Dominant language
- JavaScript
- Stars
- 17k
- Forks
- 3.4k
- Avg merge
- 7h 42m
- Merged PRs (30d)
- 26
Description
This came up for fixes to svg-gradient() (https://github.com/less/less.js/pull/3261). There are no automated visual regression tests, so it might be good to do so for functions that create visual assets. See: https://github.com/garris/BackstopJS
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 reviewing the svg-gradient() fixes in PR 3261 and the BackstopJS project to understand the proposed visual regression approach. Identify which Less functions create visual assets and define representative cases for them. Done means automated Backstop visual regression coverage is added for the agreed functions and passes consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100