Basic Testing
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 98
- PR merge metrics
- No merged PRs in 30d
Description
What would a basic testing infrastructure look like. Due to the nature of the code and the need for rapid iteration, unit testing won't get us very far.
Can we set up some sort of testing framework where simple graphics programs built against the latest version of piet and then diffed with known good images. This could work with the direct-2d and cairo backends but is problematic with a web based backend. How robust would this testing be? Would it easily miss real issues or report failures on things that aren't actually failures?
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 evaluating the proposed image-diff testing approach for simple graphics programs built against the latest piet version. Compare its applicability to the direct-2d and cairo backends with the problems noted for a web-based backend. Done means defining a testing framework and assessing false positives, false negatives, and backend coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100