impero-com / impero-com/typebinder
Proper test suite
Open
enhancement
help wanted
- Dominant language
- Rust
- Stars
- 22
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
We should have a proper way to test the output of typebinder, in a way that will serve both as a demo and as test coverage.
I'm opened to ideas that would be suggested here, and I'll come up with a draft idea soon-ish.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are identified in the issue. Start by reviewing how typebinder currently produces TypeScript definitions and what test setup exists; done means a test approach that also serves as a usable demo and provides output coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100