testdouble / testdouble/suture
Register a known side effect
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 1.4k
- Forks
- 27
- Avg merge
- 27m
- Merged PRs (30d)
- 2
Description
It'd be neat to identify a method you associate with a side effect (like an http.post) and then wrap it. Still calling through but warning the user?
As for default registrations, I suspect vcr or webmock might have some prior art on this from an HTTP perspective? Would be good to have an API that could handle database/socket connections as well.
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 by reviewing Suture's existing public API and how it handles method wrapping. Compare possible registrations for HTTP, database, and socket side effects, then define an API that preserves the original call while warning users; done means the scope and behavior are specified and covered for these categories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100