apple / apple/swift-distributed-actors
TestKit cleanups and making consistent
- Dominant language
- Swift
- Stars
- 679
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Description
E.g. how to use expectMessage within eventually blocks?
Check if we are missing any overloads.
Decide what to do about ShouldMatchers -- internally we want them, but not as part of API or we're ok to expose them? Go we guarantee bin/source compat for the test utils?
Contributor guide
Research direction
Start by locating the TestKit entry points and existing uses of expectMessage within eventually blocks. Audit the available overloads and the ShouldMatchers exposure, then resolve the stated API and binary/source compatibility questions. Done means the cleanup scope and compatibility policy are agreed and the affected test utilities are consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100