typelevel / typelevel/cats-effect-testing
Implement ScalaTest ioRetrying with a generic effect type
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 194
- Forks
- 42
- Avg merge
- 5h 16m
- Merged PRs (30d)
- 1
Description
In order to use the ioRetrying defined below, we need a concrete IO. I think it would better for this to take a generic effect type (even though it would use IO in the base trait), so that helper traits don't need to be tied to IO.
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 reading scalatest/jvm/src/main/scala/cats/effect/testing/scalatest/AsyncIOSpec.scala at the linked ioRetrying definition. Trace how the base trait currently uses IO and how helper traits depend on it. Done means ScalaTest ioRetrying accepts a generic effect type while the base trait can still use IO and helper traits are no longer tied to IO.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100