Melsaeed276 / Melsaeed276/Hatim_Program
prayer-times: testing strategy and automated coverage
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Goal
Define and implement testing coverage for prayer-time module.
Scope
- Unit tests for domain logic (current/next/countdown calculations).
- Data-layer tests for parsing and cache strategy.
- Widget tests for home prayer cards and state handling.
- Integration tests for main user flow:
- grant/deny location
- fetch schedule
- show current/next/countdown
- notification scheduling behavior
Acceptance Criteria
- Critical prayer-time logic has unit test coverage.
- Core UI states are covered by widget tests.
- Integration happy-path exists and runs in CI.
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 locating the prayer-time module, its data layer, home prayer cards, notification scheduling, and CI configuration. Review the existing implementation and tests, then cover calculation logic, parsing and caching, core widget states, and the listed happy-path flow so the acceptance criteria run in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100