Re-add Flow's tests
Open
- Dominant language
- Kotlin
- Stars
- 2.2k
- Forks
- 116
- Avg merge
- 1h 36m
- Merged PRs (30d)
- 8
Description
I omitted them from #51 because our internals have changed significantly and my testing approach then was wrong. This issue tracks re-introducing the tests
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing issue #51 and the current Flow-related internals and tests; the payload does not name specific files or entry points. Identify which tests were omitted and adapt them to the changed testing approach. Done means the Flow tests are restored and pass with the current implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100