rubyforgood / rubyforgood/alongwithyou
Manually test the app on a simulator or device
Open
Nobody has claimed this yet.
needs-verification
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 4
- Avg merge
- 9h 34m
- Merged PRs (30d)
- 16
Description
Every claim about runtime UI behavior in this review is from static analysis only. Nothing has actually run the app on a simulator or device yet, worth doing before treating the accessibility/timeout/retry findings as fully confirmed in practice.
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 running the app on a simulator or device, then exercise the accessibility, timeout, and retry scenarios referenced in the issue. Done means each static-analysis finding is confirmed or refuted through runtime testing and the results are recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100