Test Plan & Coverage Wiki Page

🧪 Test Plan & Coverage (MVP)

1. Testing Strategy

This project follows a layered testing approach to ensure both technical correctness and user acceptance.

Backend (Spring Boot)

• Unit Tests: Business logic validation (authentication, matching, request flow)
• Integration Tests: Controller–Service–Repository flow with H2 database
• API Tests: Endpoint validation (status codes, responses, validation rules)
• Mocking: External dependencies where needed

Frontend (React Web)

• Component rendering and state testing
• Form validation and user interaction tests
• API integration with mocked backend
• Core flows (login, profile, mentorship request)

Mobile (React Native)

• Screen and component testing
• API integration tests
• Core flows (authentication, profile, mentorship actions)

---

2. Test Plan Coverage (MVP)

The test plan validates all MVP features and ensures that the system satisfies user expectations.

Covered Features

• Authentication (registration, login, JWT handling)
• Profile management (view and edit)
• Mentor/mentee matching
• Mentorship request creation and response (accept/reject)
• Mentorship relationship state management (PENDING, ACTIVE, REJECTED)
• Active mentorship listing
• Mentor availability management
• Basic notification triggering

Acceptance Criteria & Scenarios

The MVP is considered acceptable if the following flows work correctly:

• Users can register, log in, and remain authenticated
• Users can view and update their profiles
• Users can discover mentors or mentees through matching
• Users can send mentorship requests
• Mentors can accept or reject requests
• Mentorship relationships correctly transition between:
  • PENDING → ACTIVE → REJECTED
• Users can view active mentorships
• Mentors can manage their availability
• System triggers basic notifications for key actions
• All flows work consistently across backend, web, and mobile

---

3. Coverage Goals

• Service Layer: ≥ 80% logic coverage
• Critical APIs: 100% tested
• Core User Flows: 100% covered
• Frontend & Mobile: All critical journeys tested

Priority: User flow correctness over raw code coverage

---

4. Definition of Done (MVP)

The MVP is considered complete when:

• All core user flows execute without errors
• Backend, Web, and Mobile systems are consistent
• Authentication and mentorship workflows function correctly
• Matching and profile features behave as expected
• System is stable under normal usage