ChinmayOnGithub / ChinmayOnGithub/tracker
[Testing] Establish end-to-end critical user journey regression suite
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 16m
- Merged PRs (30d)
- 3
Description
Add browser-level tests covering sign in, Today load, calendar event creation, task creation, activity completion, event drag/resize, date navigation, refresh persistence, offline mutation, reconnect synchronization, and Google Calendar event visibility. These are release-blocking journeys and must run 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
The issue names no test files, browser framework, or CI entry point. Start by locating the repository’s existing test and CI setup, then map each listed journey to coverage. Done means all specified flows run as release-blocking CI tests, including offline/reconnect synchronization and Google Calendar visibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100