Testing: Final End to End Testing (Part 1)

[RishiGoswami-code]

Overview

---

A user doesn't care whether the database works, React works, AI works, or APIs work. They only care that they can get the right and smooth analysis, check understand the problem, gets report, and solution or not.

For OzymorLab, I would divide testing into these phases:

Phase 1: Authentication Testing

Test every possible path.

Student

• Sign Up
• Sign In
• Logout
• Forgot Password
• Reset Password
• Email Verification
• Session Expiry
• Login with invalid credentials
• Multiple tab login

Bugs to look for

• Broken redirects
• Infinite loading
• Incorrect error messages
• Session persistence issues

---

Phase 2: Student Journey Testing

Upload Answer Sheet

Test:

• PDF upload
• Large PDF upload
• Multiple uploads
• Corrupted PDF
• Empty PDF
• Unsupported format
• Upload cancellation

Verify:

• File stored correctly
• Progress shown
• Credits deducted correctly
• Submission created

---

AI Evaluation

Verify:

• * Evaluation starts
• * Status changes
• * Progress visible
• * Evaluation completes
• * Marks generated
• * Suggestions generated

Test edge cases:

• * 1 page
• * 5 pages
• * 20 pages
• * Handwritten pages
• * Low quality images
• * Blurry scans

Bugs

• * AI timeout
• * Wrong marks
• * Missing pages
• * Duplicate evaluations

---

Phase 3: Submission Dashboard

Verify:

• * Submission history
• * Search
• * Pagination
• * Filters
• * Download reports
• * Open previous reports

Check:

• * Mobile
• * Tablet
• * Desktop

---

Phase 4: Credits System

Very important.

Test:

• * Buy credits
• * Credit deduction
• * Refund flow
• * Failed payment
• * Double payment
• * Refresh during payment

Verify:

• * Credits never become negative
• * No duplicate transactions

---

Phase 5: Admin Panel

Verify:

• * Login
• * Student list
• * Submission list
• * Analytics
• * Revenue dashboard
• * User blocking
• * Credit management

Check authorization:

• * Student cannot access admin routes
• * API access restricted