-
Notifications
You must be signed in to change notification settings - Fork 0
Lab 9 Report
burakogut5 edited this page Apr 30, 2026
·
32 revisions
Author: [Burak Ögüt]
Feature: Mentor Cross-Profile Exploration, Inter-Mentor Communication, and Mentee Progress Tracking
Scenario: A mentor (Mentor A) browses the platform to view the public profiles of peer mentors for networking purposes, initiates communication with another mentor, and then switches context to review the ongoing progress of their own mentees — including assigned tasks, submitted work, and milestone completion.
| Name | ID | Prerequisite | Instruction | Expectation | Result | Note |
|---|---|---|---|---|---|---|
| Mentor navigates to Explore page as mentor role | TC-MNT-01 | Mentor A is logged in on mobile; at least 2 other mentor accounts exist in the system | Open the app, navigate to the Explore / Discover tab | Explore tab loads without error; page displays other mentor profiles (name, area of expertise, availability status) — not mentee profiles | Pass / Fail | Mentor role should see a mentor-oriented Explore view, not the mentee-facing mentor list |
| Mentor views another mentor's public profile | TC-MNT-02 | TC-MNT-01 passed; Mentor B has a fully completed public profile (bio, skills, mentoring goals, availability) | Tap on Mentor B's card in the Explore list | Mentor B's public profile screen opens; displays: full name, expertise areas, mentoring goals, availability slots, and mentee capacity status; surname is fully visible (surname hiding applies only to mentee candidates) | Pass / Fail | Requirement 1.2.2.1: profiles include background, goals, skills, interests |
| Mentor checks own profile visibility settings | TC-MNT-03 | Mentor A is on their own Profile tab | Navigate to Profile → Edit Profile; locate the Profile Visibility toggle | Visibility toggle is present and shows current state (Public / Private); changing and saving persists correctly on reload | Pass / Fail | Requirement 1.2.2.3: users can control profile visibility |
| Mentor initiates message to another mentor | TC-MNT-04 | TC-MNT-02 passed; messaging feature is enabled between mentors; Mentor A and Mentor B are both active | From Mentor B's public profile screen, tap "Send Message" or equivalent CTA; type "Hello, I'd like to discuss a shared mentee topic." and send | Message is delivered; conversation thread appears in Mentor A's Messages tab; Mentor B receives a notification | Pass / Fail | Requirement 1.1.3.5 (mentor–mentor messaging); currently marked out of scope for final milestone — mark Result as N/A if feature not yet live |
| Mentor views active mentees on Home dashboard | TC-MNT-05 | Mentor A has at least 2 active mentees (mentorship requests previously accepted) | Navigate to the Home tab | Home dashboard displays the list of active mentees with their names, profile photos, and mentorship start dates; mentee count (e.g., 2/5) matches actual count | Pass / Fail | Requirement 1.1.1.2.11: mentor manages multiple mentees up to max capacity |
| Mentor opens a specific mentee's progress page | TC-MNT-06 | TC-MNT-05 passed; Mentee X has at least one task assigned | Tap on Mentee X's card from the Home dashboard | Mentee X's progress detail screen opens; displays: active tasks with status (Not Started / In Progress / Completed), milestone list, and overall goal completion percentage | Pass / Fail | Requirement 1.1.5.1–1.1.5.4: task assignment, progress tracking, milestone management |
| Mentor assigns a new task to mentee | TC-MNT-07 | TC-MNT-06 passed; Mentor A is on Mentee X's progress screen | Tap "Add Task"; fill in Title: "Write a REST API", Description: "Implement a basic CRUD API using Spring Boot", Due Date: 7 days from today; tap Save | Task appears in Mentee X's task list with status "Not Started"; Mentee X receives a notification about the new task assignment | Pass / Fail | Requirement 1.1.5.1: assign tasks to mentees; 1.1.5.5: task notifications |
| Mentor reviews a task submitted by mentee | TC-MNT-08 | TC-MNT-07 passed; Mentee X has submitted work for the assigned task (status changed to "Submitted") | On Mentee X's progress screen, tap the submitted task; review attached submission (file or link) | Submission details are displayed; Mentor A can see the submitted content; "Approve" and "Request Revision" actions are available | Pass / Fail | Requirement 1.1.5.3: mentor reviews submitted work; 1.1.5.6: feedback flow |
| Mentor provides feedback and approves task | TC-MNT-09 | TC-MNT-08 passed; Mentor A is viewing Mentee X's submitted task | Enter feedback: "Great work, the endpoint structure is clean. Add error handling next."; tap "Approve" | Task status changes to "Completed"; feedback text is saved and visible to Mentee X; overall goal completion percentage increases; Mentee X receives a notification | Pass / Fail | Requirement 1.1.5.3 (feedback), 1.1.5.4 (milestone tracking), 2.3.1 (notification within 5 seconds) |
| Mentor views milestone completion summary | TC-MNT-10 | TC-MNT-09 passed; at least one milestone has all sub-tasks completed | Navigate to Mentee X's progress screen; scroll to Milestones section | Milestone is marked as completed with a timestamp; progress bar reflects 100% for that milestone; historical task completions are listed in chronological order | Pass / Fail | Requirement 1.1.5.2: milestone tracking; 1.1.5.8: goal completion visibility |
| Mentor checks second mentee's progress independently | TC-MNT-11 | Mentor A has a second active mentee (Mentee Y) with different task statuses | Navigate back to Home dashboard; tap on Mentee Y's card | Mentee Y's progress screen opens independently with Mentee Y's own tasks and milestones; Mentee X's data is not shown or mixed in | Pass / Fail | Verifies data isolation between concurrent mentee relationships; Requirement 1.1.1.2.11 |
| Mentor logs out and re-logs in; verifies data persistence | TC-MNT-12 | TC-MNT-07 through TC-MNT-10 completed | Log out from Mentor A's account; log back in; navigate to Mentee X's progress screen | All previously assigned tasks, submitted work, feedback, and milestone status are intact and correctly displayed; no data loss across session | Pass / Fail | Validates backend persistence (Requirement 2.1.1: system availability; data durability) |
Team Members
- Lab 1 Report (12/02/2026)
- Lab 2 Report (19/02/2026)
- Lab 3 Report (26/02/2026)
- Lab 4 Report (05/03/2026)
- Lab 5 Report (12/03/2026)
- Lab 6 Report (26/03/2026)
- Lab 7 Report (02/04/2026)
- Lab 8 Report (18/04/2026)
- Lab 9 Report (30/04/2026)
- Lab 10 Report (07/05/2026)
- Weekly Meeting Notes Template
- Lab Meeting 1 (12.02.2026)
- Weekly Meeting 1 (16.02.2026)
- Weekly Meeting 2 (24.02.2026)
- Weekly Meeting 3 (04.03.2026)
- Weekly Meeting 4 (11.03.2026)
- Weekly Meeting 5 (23.03.2026)
- Weekly Meeting 6 (29.03.2026)
- Weekly Meeting 7 (11.04.2026)
- Weekly Meeting 8 (28.04.2026)
- Weekly Meeting 9 (10.05.2026)
- Use Case Diagram 1 (New Mentor User for Mobile Scenario)
- Use Case Diagram 2 (Mentor-Mentee Matching Scenario)
- Use Case Diagram 3 (New Mentee User Scenario)
- Final Use Case Diagram
- MVP Use Case Diagram
- All Sequence Diagrams
- Sequence Diagram: Mentee Matching
- Sequence Diagram: Mentor Matching
- Sequence Diagram: Mentorship Management
- Sequence Diagram: Registration
- Sequence Diagram: Cancelling Mentorship Relationship and Auto Ban
- Sequence Diagram: Login-Logout
- Sequence Diagram: Reporting-User
- Sequence Diagram: Mentor Profile Management
- MVP Sequence Diagrams
- Test Plan & Coverage (MVP)
- Acceptance Testing Strategy
- Acceptance Tests
- Test Data Strategy
- Web Frontend Test Report
- Amin Abu-Hilga
- Övgü Su Afşar
- Muhammet Sami Çakmak
- Beratcan Doğan
- İbrahim Kayan
- Burak Ögüt
- Mehmet Bora Sarıoğlu
- Future Work (reference, not a deliverable)