Add authenticated E2E smoke tests with seeded student tutor and admin users

Open
#140 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
supabase, typescript
Domain
authentication, testing

Research direction

Start with .tmp/sessions/2026-03-29-corved-e2e/context.md, then review the launch checklist in docs/MVP.md and the integration smoke test item in docs/plan-CorvEd.md. Identify the existing E2E entry points and define deterministic local or CI fixtures for student/parent, tutor, and admin roles. Done means the three role-based flows and wrong-role route checks run without production secrets, with failures linked to separate implementation issues.

Written by the indexing model from the issue text.

Description

Admin DevOps P1 Payment Sessions Student Task Tutor

Context

The March E2E context file shows authenticated browser testing was started but not completed. Current automated coverage is useful, but the launch-critical flows are role-based and need seeded user coverage.

Acceptance criteria

  • Add a documented seeded-user setup for student/parent, tutor, and admin roles in local Supabase or test fixtures.
  • Cover at least one student request/payment flow, one admin payment/matching/session generation flow, and one tutor session update flow.
  • Include route-protection checks for wrong-role access.
  • Keep tests deterministic and safe to run locally/CI without production secrets.
  • Link failures to separate implementation issues rather than hiding them in the test work.

References

  • .tmp/sessions/2026-03-29-corved-e2e/context.md
  • docs/MVP.md launch checklist
  • docs/plan-CorvEd.md integration smoke test item
Dominant language
TypeScript
Stars
5
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Taleef7/CorvEd

All issues in Taleef7/CorvEd

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.