# 2. Collaborative Tracking & Milestones — Test Cases

User Type: **Parent**
Source: *Mi Digital Academy - Education CRM Features Document*
Spec: collaborative_tracking_milestones.md — every feature, sub-feature, and rule covered

---

## Test Execution Policy
- Zero tolerance: any deviation from documented behavior = FAILED = bug
- Every bug is immediately logged/reported (Bug ID, feature, sub-feature, expected vs actual, severity) and fixed 100% before the group passes
- Feature group passes only at 100% test pass rate

## Coverage Matrix
| Feature | Sub-feature / Rule | Test IDs |
|---------|--------------------|----------|
| 2.1 Shared Progress View | Shared view of the child's progress | TC-PT-9-02-001 |
| 2.1 Shared Progress View | Courses completed and scores | TC-PT-9-02-002 |
| 2.1 Shared Progress View | Time spent on learning | TC-PT-9-02-003 |
| 2.1 Shared Progress View | Parent can add encouraging notes | TC-PT-9-02-004 |
| 2.1 Shared Progress View | Progress visible to both Parent and child | TC-PT-9-02-005 |
| 2.1 Shared Progress View | Shared view available on web and mobile | TC-PT-9-02-006 |
| 2.1 Shared Progress View | View event logging (viewed, noted) | TC-PT-9-02-007 |
| 2.1 Shared Progress View | Audit logging of the shared progress view | TC-PT-9-02-008 |
| 2.1 Shared Progress View | Rule: The progress is shared between the Parent and the child. | TC-PT-9-02-001 |
| 2.1 Shared Progress View | Rule: The Parent can add encouraging notes. | TC-PT-9-02-002 |
| 2.1 Shared Progress View | Rule: The progress is visible to both. | TC-PT-9-02-003 |
| 2.1 Shared Progress View | Rule: View events (viewed, noted) are logged with the account and the timestamp. | TC-PT-9-02-004 |
| 2.1 Shared Progress View | Rule: The shared progress view is audit-logged with the account and the timestamp. | TC-PT-9-02-005 |
| 2.2 Milestone Tracking | Milestone types (completion, score, streak) | TC-PT-9-02-009 |
| 2.2 Milestone Tracking | Milestones reached | TC-PT-9-02-010 |
| 2.2 Milestone Tracking | Next milestones to aim for | TC-PT-9-02-011 |
| 2.2 Milestone Tracking | Milestone progress indicator | TC-PT-9-02-012 |
| 2.2 Milestone Tracking | Milestone history | TC-PT-9-02-013 |
| 2.2 Milestone Tracking | Milestones visible to both Parent and child | TC-PT-9-02-014 |
| 2.2 Milestone Tracking | Milestone event logging (reached) | TC-PT-9-02-015 |
| 2.2 Milestone Tracking | Audit logging of the milestone tracking | TC-PT-9-02-016 |
| 2.2 Milestone Tracking | Rule: The milestones are completion, score, and streak types. | TC-PT-9-02-009 |
| 2.2 Milestone Tracking | Rule: The milestones reached and upcoming are shown. | TC-PT-9-02-010 |
| 2.2 Milestone Tracking | Rule: The milestones are visible to both the Parent and the child. | TC-PT-9-02-011 |
| 2.2 Milestone Tracking | Rule: Milestone events (reached) are logged with the account and the timestamp. | TC-PT-9-02-012 |
| 2.2 Milestone Tracking | Rule: The milestone tracking is audit-logged with the account and the timestamp. | TC-PT-9-02-013 |
| 2.3 Study Check-ins | Schedule a study check-in | TC-PT-9-02-017 |
| 2.3 Study Check-ins | Ad-hoc study check-in | TC-PT-9-02-018 |
| 2.3 Study Check-ins | Check-in topics (study, challenges, plans) | TC-PT-9-02-019 |
| 2.3 Study Check-ins | Check-in notes saved | TC-PT-9-02-020 |
| 2.3 Study Check-ins | Check-in history | TC-PT-9-02-021 |
| 2.3 Study Check-ins | Check-ins visible to both Parent and child | TC-PT-9-02-022 |
| 2.3 Study Check-ins | Check-in event logging (scheduled, completed) | TC-PT-9-02-023 |
| 2.3 Study Check-ins | Audit logging of the study check-ins | TC-PT-9-02-024 |
| 2.3 Study Check-ins | Rule: The check-in can be scheduled or ad-hoc. | TC-PT-9-02-017 |
| 2.3 Study Check-ins | Rule: The check-in notes are saved. | TC-PT-9-02-018 |
| 2.3 Study Check-ins | Rule: The check-in is visible to both the Parent and the child. | TC-PT-9-02-019 |
| 2.3 Study Check-ins | Rule: Check-in events (scheduled, completed) are logged with the account and the timestamp. | TC-PT-9-02-020 |
| 2.3 Study Check-ins | Rule: The study check-ins is audit-logged with the account and the timestamp. | TC-PT-9-02-021 |

## 2.1 Shared Progress View

### TC-PT-9-02-001 — Shared view of the child's progress
**Type:** Positive
**Covers:** 2.1 → Shared view of the child's progress; Rule: The progress is shared between the Parent and the child.
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Shared view of the child's progress.
2. Observe the result and verify the full behavior: Shared view of the child's progress.
**Expected Result:** Shared view of the child's progress — delivered exactly as documented.
**Priority:** Critical

### TC-PT-9-02-002 — Courses completed and scores
**Type:** Positive
**Covers:** 2.1 → Courses completed and scores; Rule: The Parent can add encouraging notes.
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Courses completed and scores.
2. Observe the result and verify the full behavior: Courses completed and scores.
**Expected Result:** Courses completed and scores — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-003 — Time spent on learning
**Type:** Positive
**Covers:** 2.1 → Time spent on learning; Rule: The progress is visible to both.
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Time spent on learning.
2. Observe the result and verify the full behavior: Time spent on learning.
**Expected Result:** Time spent on learning — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-004 — Parent can add encouraging notes
**Type:** Positive
**Covers:** 2.1 → Parent can add encouraging notes; Rule: View events (viewed, noted) are logged with the account and the timestamp.
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Parent can add encouraging notes.
2. Observe the result and verify the full behavior: Parent can add encouraging notes.
**Expected Result:** Parent can add encouraging notes — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-005 — Progress visible to both Parent and child
**Type:** Positive
**Covers:** 2.1 → Progress visible to both Parent and child; Rule: The shared progress view is audit-logged with the account and the timestamp.
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Progress visible to both Parent and child.
2. Observe the result and verify the full behavior: Progress visible to both Parent and child.
**Expected Result:** Progress visible to both Parent and child — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-006 — Shared view available on web and mobile
**Type:** Positive
**Covers:** 2.1 → Shared view available on web and mobile
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Shared view available on web and mobile.
2. Observe the result and verify the full behavior: Shared view available on web and mobile.
**Expected Result:** Shared view available on web and mobile — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-007 — View event logging (viewed, noted)
**Type:** Positive
**Covers:** 2.1 → View event logging (viewed, noted)
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: View event logging (viewed.
2. Observe the result and verify the full behavior: View event logging (viewed, noted).
**Expected Result:** View event logging (viewed, noted) — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-008 — Audit logging of the shared progress view
**Type:** Positive
**Covers:** 2.1 → Audit logging of the shared progress view
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, perform the action associated with: Audit logging of the shared progress view.
2. Open the relevant activity / audit log and verify the event is recorded with the account, the action, and the timestamp.
**Expected Result:** The action is audit-logged — the account, the action, and the timestamp are recorded.
**Priority:** Critical

## 2.2 Milestone Tracking

### TC-PT-9-02-009 — Milestone types (completion, score, streak)
**Type:** Positive
**Covers:** 2.2 → Milestone types (completion, score, streak); Rule: The milestones are completion, score, and streak types.
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Milestone types (completion.
2. Observe the result and verify the full behavior: Milestone types (completion, score, streak).
**Expected Result:** Milestone types (completion, score, streak) — delivered exactly as documented.
**Priority:** Critical

### TC-PT-9-02-010 — Milestones reached
**Type:** Positive
**Covers:** 2.2 → Milestones reached; Rule: The milestones reached and upcoming are shown.
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Milestones reached.
2. Observe the result and verify the full behavior: Milestones reached.
**Expected Result:** Milestones reached — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-011 — Next milestones to aim for
**Type:** Positive
**Covers:** 2.2 → Next milestones to aim for; Rule: The milestones are visible to both the Parent and the child.
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Next milestones to aim for.
2. Observe the result and verify the full behavior: Next milestones to aim for.
**Expected Result:** Next milestones to aim for — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-012 — Milestone progress indicator
**Type:** Positive
**Covers:** 2.2 → Milestone progress indicator; Rule: Milestone events (reached) are logged with the account and the timestamp.
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Milestone progress indicator.
2. Observe the result and verify the full behavior: Milestone progress indicator.
**Expected Result:** Milestone progress indicator — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-013 — Milestone history
**Type:** Positive
**Covers:** 2.2 → Milestone history; Rule: The milestone tracking is audit-logged with the account and the timestamp.
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Milestone history.
2. Observe the result and verify the full behavior: Milestone history.
**Expected Result:** Milestone history — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-014 — Milestones visible to both Parent and child
**Type:** Positive
**Covers:** 2.2 → Milestones visible to both Parent and child
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Milestones visible to both Parent and child.
2. Observe the result and verify the full behavior: Milestones visible to both Parent and child.
**Expected Result:** Milestones visible to both Parent and child — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-015 — Milestone event logging (reached)
**Type:** Positive
**Covers:** 2.2 → Milestone event logging (reached)
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Milestone event logging (reached).
2. Observe the result and verify the full behavior: Milestone event logging (reached).
**Expected Result:** Milestone event logging (reached) — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-016 — Audit logging of the milestone tracking
**Type:** Positive
**Covers:** 2.2 → Audit logging of the milestone tracking
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, perform the action associated with: Audit logging of the milestone tracking.
2. Open the relevant activity / audit log and verify the event is recorded with the account, the action, and the timestamp.
**Expected Result:** The action is audit-logged — the account, the action, and the timestamp are recorded.
**Priority:** Critical

## 2.3 Study Check-ins

### TC-PT-9-02-017 — Schedule a study check-in
**Type:** Positive
**Covers:** 2.3 → Schedule a study check-in; Rule: The check-in can be scheduled or ad-hoc.
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Schedule a study check-in.
2. Observe the result and verify the full behavior: Schedule a study check-in.
**Expected Result:** Schedule a study check-in — delivered exactly as documented.
**Priority:** Critical

### TC-PT-9-02-018 — Ad-hoc study check-in
**Type:** Positive
**Covers:** 2.3 → Ad-hoc study check-in; Rule: The check-in notes are saved.
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Ad-hoc study check-in.
2. Observe the result and verify the full behavior: Ad-hoc study check-in.
**Expected Result:** Ad-hoc study check-in — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-019 — Check-in topics (study, challenges, plans)
**Type:** Positive
**Covers:** 2.3 → Check-in topics (study, challenges, plans); Rule: The check-in is visible to both the Parent and the child.
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Check-in topics (study.
2. Observe the result and verify the full behavior: Check-in topics (study, challenges, plans).
**Expected Result:** Check-in topics (study, challenges, plans) — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-020 — Check-in notes saved
**Type:** Positive
**Covers:** 2.3 → Check-in notes saved; Rule: Check-in events (scheduled, completed) are logged with the account and the timestamp.
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Check-in notes saved.
2. Observe the result and verify the full behavior: Check-in notes saved.
**Expected Result:** Check-in notes saved — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-021 — Check-in history
**Type:** Positive
**Covers:** 2.3 → Check-in history; Rule: The study check-ins is audit-logged with the account and the timestamp.
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Check-in history.
2. Observe the result and verify the full behavior: Check-in history.
**Expected Result:** Check-in history — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-022 — Check-ins visible to both Parent and child
**Type:** Positive
**Covers:** 2.3 → Check-ins visible to both Parent and child
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Check-ins visible to both Parent and child.
2. Observe the result and verify the full behavior: Check-ins visible to both Parent and child.
**Expected Result:** Check-ins visible to both Parent and child — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-023 — Check-in event logging (scheduled, completed)
**Type:** Positive
**Covers:** 2.3 → Check-in event logging (scheduled, completed)
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, set up the precondition and perform: Check-in event logging (scheduled.
2. Observe the result and verify the full behavior: Check-in event logging (scheduled, completed).
**Expected Result:** Check-in event logging (scheduled, completed) — delivered exactly as documented.
**Priority:** High

### TC-PT-9-02-024 — Audit logging of the study check-ins
**Type:** Positive
**Covers:** 2.3 → Audit logging of the study check-ins
**Preconditions:** A Parent account is active and the Parent is in the state required for this behavior.
**Steps:**
1. As a Parent, perform the action associated with: Audit logging of the study check-ins.
2. Open the relevant activity / audit log and verify the event is recorded with the account, the action, and the timestamp.
**Expected Result:** The action is audit-logged — the account, the action, and the timestamp are recorded.
**Priority:** Critical