# 2. Updates & Concerns — Test Cases

User Type: **Parent**
Source: *Mi Digital Academy - Education CRM Features Document*
Spec: updates_concerns.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 Request a Progress Update | Request a progress update from the teacher | TC-PT-6-02-001 |
| 2.1 Request a Progress Update | Specify what to include in the update | TC-PT-6-02-002 |
| 2.1 Request a Progress Update | Teacher provides the update | TC-PT-6-02-003 |
| 2.1 Request a Progress Update | Notification when the update is available | TC-PT-6-02-004 |
| 2.1 Request a Progress Update | Update history | TC-PT-6-02-005 |
| 2.1 Request a Progress Update | Requests available on web and mobile | TC-PT-6-02-006 |
| 2.1 Request a Progress Update | Request event logging (submitted, fulfilled) | TC-PT-6-02-007 |
| 2.1 Request a Progress Update | Audit logging of the request a progress update | TC-PT-6-02-008 |
| 2.1 Request a Progress Update | Rule: The request specifies what to include. | TC-PT-6-02-001 |
| 2.1 Request a Progress Update | Rule: The teacher provides the update. | TC-PT-6-02-002 |
| 2.1 Request a Progress Update | Rule: A notification is sent when the update is available. | TC-PT-6-02-003 |
| 2.1 Request a Progress Update | Rule: Request events (submitted, fulfilled) are logged with the account and the timestamp. | TC-PT-6-02-004 |
| 2.1 Request a Progress Update | Rule: The request a progress update is audit-logged with the account and the timestamp. | TC-PT-6-02-005 |
| 2.2 Discuss a Concern | Raise a concern with the teacher | TC-PT-6-02-009 |
| 2.2 Discuss a Concern | Describe the concern (performance, behavior, learning) | TC-PT-6-02-010 |
| 2.2 Discuss a Concern | Teacher responds with perspective and plan | TC-PT-6-02-011 |
| 2.2 Discuss a Concern | Concern status (open, in progress, resolved) | TC-PT-6-02-012 |
| 2.2 Discuss a Concern | Concern resolution tracking | TC-PT-6-02-013 |
| 2.2 Discuss a Concern | Concerns available on web and mobile | TC-PT-6-02-014 |
| 2.2 Discuss a Concern | Concern event logging (raised, responded, resolved) | TC-PT-6-02-015 |
| 2.2 Discuss a Concern | Audit logging of the discuss a concern | TC-PT-6-02-016 |
| 2.2 Discuss a Concern | Rule: The concern is described by the Parent. | TC-PT-6-02-009 |
| 2.2 Discuss a Concern | Rule: The teacher responds with a plan. | TC-PT-6-02-010 |
| 2.2 Discuss a Concern | Rule: The concern status is tracked to resolution. | TC-PT-6-02-011 |
| 2.2 Discuss a Concern | Rule: Concern events (raised, responded, resolved) are logged with the account and the timestamp. | TC-PT-6-02-012 |
| 2.2 Discuss a Concern | Rule: The discuss a concern is audit-logged with the account and the timestamp. | TC-PT-6-02-013 |
| 2.3 Teacher Feedback on Concerns | Teacher feedback on a concern | TC-PT-6-02-017 |
| 2.3 Teacher Feedback on Concerns | Teacher's assessment of the concern | TC-PT-6-02-018 |
| 2.3 Teacher Feedback on Concerns | Actions taken by the teacher | TC-PT-6-02-019 |
| 2.3 Teacher Feedback on Concerns | Outcome of the concern | TC-PT-6-02-020 |
| 2.3 Teacher Feedback on Concerns | Follow-up on the feedback | TC-PT-6-02-021 |
| 2.3 Teacher Feedback on Concerns | Feedback available on web and mobile | TC-PT-6-02-022 |
| 2.3 Teacher Feedback on Concerns | Feedback event logging (received, followed up) | TC-PT-6-02-023 |
| 2.3 Teacher Feedback on Concerns | Audit logging of the teacher feedback on concerns | TC-PT-6-02-024 |
| 2.3 Teacher Feedback on Concerns | Rule: The feedback is on a raised concern. | TC-PT-6-02-017 |
| 2.3 Teacher Feedback on Concerns | Rule: The feedback includes the assessment, actions, and outcome. | TC-PT-6-02-018 |
| 2.3 Teacher Feedback on Concerns | Rule: A follow-up can be made on the feedback. | TC-PT-6-02-019 |
| 2.3 Teacher Feedback on Concerns | Rule: Feedback events (received, followed up) are logged with the account and the timestamp. | TC-PT-6-02-020 |
| 2.3 Teacher Feedback on Concerns | Rule: The teacher feedback on concerns is audit-logged with the account and the timestamp. | TC-PT-6-02-021 |

## 2.1 Request a Progress Update

### TC-PT-6-02-001 — Request a progress update from the teacher
**Type:** Positive
**Covers:** 2.1 → Request a progress update from the teacher; Rule: The request specifies what to include.
**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: Request a progress update from the teacher.
2. Observe the result and verify the full behavior: Request a progress update from the teacher.
**Expected Result:** Request a progress update from the teacher — delivered exactly as documented.
**Priority:** Critical

### TC-PT-6-02-002 — Specify what to include in the update
**Type:** Positive
**Covers:** 2.1 → Specify what to include in the update; Rule: The teacher provides the update.
**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: Specify what to include in the update.
2. Observe the result and verify the full behavior: Specify what to include in the update.
**Expected Result:** Specify what to include in the update — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-003 — Teacher provides the update
**Type:** Positive
**Covers:** 2.1 → Teacher provides the update; Rule: A notification is sent when the update is available.
**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: Teacher provides the update.
2. Observe the result and verify the full behavior: Teacher provides the update.
**Expected Result:** Teacher provides the update — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-004 — Notification when the update is available
**Type:** Positive
**Covers:** 2.1 → Notification when the update is available; Rule: Request events (submitted, fulfilled) 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: Notification when the update is available.
2. Observe the result and verify the full behavior: Notification when the update is available.
**Expected Result:** Notification when the update is available — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-005 — Update history
**Type:** Positive
**Covers:** 2.1 → Update history; Rule: The request a progress update 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: Update history.
2. Observe the result and verify the full behavior: Update history.
**Expected Result:** Update history — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-006 — Requests available on web and mobile
**Type:** Positive
**Covers:** 2.1 → Requests 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: Requests available on web and mobile.
2. Observe the result and verify the full behavior: Requests available on web and mobile.
**Expected Result:** Requests available on web and mobile — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-007 — Request event logging (submitted, fulfilled)
**Type:** Positive
**Covers:** 2.1 → Request event logging (submitted, fulfilled)
**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: Request event logging (submitted.
2. Observe the result and verify the full behavior: Request event logging (submitted, fulfilled).
**Expected Result:** Request event logging (submitted, fulfilled) — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-008 — Audit logging of the request a progress update
**Type:** Positive
**Covers:** 2.1 → Audit logging of the request a progress update
**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 request a progress update.
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 Discuss a Concern

### TC-PT-6-02-009 — Raise a concern with the teacher
**Type:** Positive
**Covers:** 2.2 → Raise a concern with the teacher; Rule: The concern is described by the Parent.
**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: Raise a concern with the teacher.
2. Observe the result and verify the full behavior: Raise a concern with the teacher.
**Expected Result:** Raise a concern with the teacher — delivered exactly as documented.
**Priority:** Critical

### TC-PT-6-02-010 — Describe the concern (performance, behavior, learning)
**Type:** Positive
**Covers:** 2.2 → Describe the concern (performance, behavior, learning); Rule: The teacher responds with a plan.
**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: Describe the concern (performance.
2. Observe the result and verify the full behavior: Describe the concern (performance, behavior, learning).
**Expected Result:** Describe the concern (performance, behavior, learning) — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-011 — Teacher responds with perspective and plan
**Type:** Positive
**Covers:** 2.2 → Teacher responds with perspective and plan; Rule: The concern status is tracked to resolution.
**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: Teacher responds with perspective and plan.
2. Observe the result and verify the full behavior: Teacher responds with perspective and plan.
**Expected Result:** Teacher responds with perspective and plan — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-012 — Concern status (open, in progress, resolved)
**Type:** Positive
**Covers:** 2.2 → Concern status (open, in progress, resolved); Rule: Concern events (raised, responded, resolved) 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: Concern status (open.
2. Observe the result and verify the full behavior: Concern status (open, in progress, resolved).
**Expected Result:** Concern status (open, in progress, resolved) — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-013 — Concern resolution tracking
**Type:** Positive
**Covers:** 2.2 → Concern resolution tracking; Rule: The discuss a concern 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: Concern resolution tracking.
2. Observe the result and verify the full behavior: Concern resolution tracking.
**Expected Result:** Concern resolution tracking — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-014 — Concerns available on web and mobile
**Type:** Positive
**Covers:** 2.2 → Concerns 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: Concerns available on web and mobile.
2. Observe the result and verify the full behavior: Concerns available on web and mobile.
**Expected Result:** Concerns available on web and mobile — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-015 — Concern event logging (raised, responded, resolved)
**Type:** Positive
**Covers:** 2.2 → Concern event logging (raised, responded, resolved)
**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: Concern event logging (raised.
2. Observe the result and verify the full behavior: Concern event logging (raised, responded, resolved).
**Expected Result:** Concern event logging (raised, responded, resolved) — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-016 — Audit logging of the discuss a concern
**Type:** Positive
**Covers:** 2.2 → Audit logging of the discuss a concern
**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 discuss a concern.
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 Teacher Feedback on Concerns

### TC-PT-6-02-017 — Teacher feedback on a concern
**Type:** Positive
**Covers:** 2.3 → Teacher feedback on a concern; Rule: The feedback is on a raised concern.
**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: Teacher feedback on a concern.
2. Observe the result and verify the full behavior: Teacher feedback on a concern.
**Expected Result:** Teacher feedback on a concern — delivered exactly as documented.
**Priority:** Critical

### TC-PT-6-02-018 — Teacher's assessment of the concern
**Type:** Positive
**Covers:** 2.3 → Teacher's assessment of the concern; Rule: The feedback includes the assessment, actions, and outcome.
**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: Teacher's assessment of the concern.
2. Observe the result and verify the full behavior: Teacher's assessment of the concern.
**Expected Result:** Teacher's assessment of the concern — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-019 — Actions taken by the teacher
**Type:** Positive
**Covers:** 2.3 → Actions taken by the teacher; Rule: A follow-up can be made on the feedback.
**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: Actions taken by the teacher.
2. Observe the result and verify the full behavior: Actions taken by the teacher.
**Expected Result:** Actions taken by the teacher — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-020 — Outcome of the concern
**Type:** Positive
**Covers:** 2.3 → Outcome of the concern; Rule: Feedback events (received, followed up) 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: Outcome of the concern.
2. Observe the result and verify the full behavior: Outcome of the concern.
**Expected Result:** Outcome of the concern — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-021 — Follow-up on the feedback
**Type:** Positive
**Covers:** 2.3 → Follow-up on the feedback; Rule: The teacher feedback on concerns 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: Follow-up on the feedback.
2. Observe the result and verify the full behavior: Follow-up on the feedback.
**Expected Result:** Follow-up on the feedback — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-022 — Feedback available on web and mobile
**Type:** Positive
**Covers:** 2.3 → Feedback 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: Feedback available on web and mobile.
2. Observe the result and verify the full behavior: Feedback available on web and mobile.
**Expected Result:** Feedback available on web and mobile — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-023 — Feedback event logging (received, followed up)
**Type:** Positive
**Covers:** 2.3 → Feedback event logging (received, followed up)
**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: Feedback event logging (received.
2. Observe the result and verify the full behavior: Feedback event logging (received, followed up).
**Expected Result:** Feedback event logging (received, followed up) — delivered exactly as documented.
**Priority:** High

### TC-PT-6-02-024 — Audit logging of the teacher feedback on concerns
**Type:** Positive
**Covers:** 2.3 → Audit logging of the teacher feedback on concerns
**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 teacher feedback on concerns.
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