# 2. Critical Performance Alerts — Test Cases

User Type: **Parent**
Source: *Mi Digital Academy - Education CRM Features Document*
Spec: critical_performance_alerts.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 Low Performance Alerts | Alert on a low quiz score | TC-PT-7-02-001 |
| 2.1 Low Performance Alerts | Alert on a failing exam result | TC-PT-7-02-002 |
| 2.1 Low Performance Alerts | Alert on a significant decline from average | TC-PT-7-02-003 |
| 2.1 Low Performance Alerts | Alert with the drop details | TC-PT-7-02-004 |
| 2.1 Low Performance Alerts | Link to the relevant report | TC-PT-7-02-005 |
| 2.1 Low Performance Alerts | Alert severity (warning, critical) | TC-PT-7-02-006 |
| 2.1 Low Performance Alerts | Alert event logging (sent, opened) | TC-PT-7-02-007 |
| 2.1 Low Performance Alerts | Audit logging of the low performance alerts | TC-PT-7-02-008 |
| 2.1 Low Performance Alerts | Rule: Alerts are sent when performance drops below a threshold. | TC-PT-7-02-001 |
| 2.1 Low Performance Alerts | Rule: The alert includes the drop details. | TC-PT-7-02-002 |
| 2.1 Low Performance Alerts | Rule: The alert severity is warning or critical. | TC-PT-7-02-003 |
| 2.1 Low Performance Alerts | Rule: Alert events (sent, opened) are logged with the account and the timestamp. | TC-PT-7-02-004 |
| 2.1 Low Performance Alerts | Rule: The low performance alerts is audit-logged with the account and the timestamp. | TC-PT-7-02-005 |
| 2.2 Missed Session Alerts | Alert on a missed live class | TC-PT-7-02-009 |
| 2.2 Missed Session Alerts | Alert on a missed mandatory study session | TC-PT-7-02-010 |
| 2.2 Missed Session Alerts | Alert on a missed assignment deadline | TC-PT-7-02-011 |
| 2.2 Missed Session Alerts | Alert with the missed item and due time | TC-PT-7-02-012 |
| 2.2 Missed Session Alerts | Missed item detail on tap | TC-PT-7-02-013 |
| 2.2 Missed Session Alerts | Alert event logging (sent, opened) | TC-PT-7-02-014 |
| 2.2 Missed Session Alerts | Audit logging of the missed session alerts | TC-PT-7-02-015 |
| 2.2 Missed Session Alerts | Rule: Alerts are sent on missed sessions and deadlines. | TC-PT-7-02-009 |
| 2.2 Missed Session Alerts | Rule: The alert includes the missed item and due time. | TC-PT-7-02-010 |
| 2.2 Missed Session Alerts | Rule: A missed item detail opens on tap. | TC-PT-7-02-011 |
| 2.2 Missed Session Alerts | Rule: Alert events (sent, opened) are logged with the account and the timestamp. | TC-PT-7-02-012 |
| 2.2 Missed Session Alerts | Rule: The missed session alerts is audit-logged with the account and the timestamp. | TC-PT-7-02-013 |
| 2.3 Engagement Drop Alerts | Alert on a significant decrease in study time | TC-PT-7-02-016 |
| 2.3 Engagement Drop Alerts | Alert on a break in the study streak | TC-PT-7-02-017 |
| 2.3 Engagement Drop Alerts | Alert on inactivity for a defined period | TC-PT-7-02-018 |
| 2.3 Engagement Drop Alerts | Alert with the engagement change | TC-PT-7-02-019 |
| 2.3 Engagement Drop Alerts | Link to the activity view | TC-PT-7-02-020 |
| 2.3 Engagement Drop Alerts | Alert event logging (sent, opened) | TC-PT-7-02-021 |
| 2.3 Engagement Drop Alerts | Audit logging of the engagement drop alerts | TC-PT-7-02-022 |
| 2.3 Engagement Drop Alerts | Rule: Alerts are sent on significant engagement drops. | TC-PT-7-02-016 |
| 2.3 Engagement Drop Alerts | Rule: The alert includes the engagement change. | TC-PT-7-02-017 |
| 2.3 Engagement Drop Alerts | Rule: A link to the activity view is included. | TC-PT-7-02-018 |
| 2.3 Engagement Drop Alerts | Rule: Alert events (sent, opened) are logged with the account and the timestamp. | TC-PT-7-02-019 |
| 2.3 Engagement Drop Alerts | Rule: The engagement drop alerts is audit-logged with the account and the timestamp. | TC-PT-7-02-020 |

## 2.1 Low Performance Alerts

### TC-PT-7-02-001 — Alert on a low quiz score
**Type:** Positive
**Covers:** 2.1 → Alert on a low quiz score; Rule: Alerts are sent when performance drops below a threshold.
**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: Alert on a low quiz score.
2. Observe the result and verify the full behavior: Alert on a low quiz score.
**Expected Result:** Alert on a low quiz score — delivered exactly as documented.
**Priority:** Critical

### TC-PT-7-02-002 — Alert on a failing exam result
**Type:** Positive
**Covers:** 2.1 → Alert on a failing exam result; Rule: The alert includes the drop details.
**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: Alert on a failing exam result.
2. Observe the result and verify the full behavior: Alert on a failing exam result.
**Expected Result:** Alert on a failing exam result — delivered exactly as documented.
**Priority:** High

### TC-PT-7-02-003 — Alert on a significant decline from average
**Type:** Positive
**Covers:** 2.1 → Alert on a significant decline from average; Rule: The alert severity is warning or critical.
**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: Alert on a significant decline from average.
2. Observe the result and verify the full behavior: Alert on a significant decline from average.
**Expected Result:** Alert on a significant decline from average — delivered exactly as documented.
**Priority:** High

### TC-PT-7-02-004 — Alert with the drop details
**Type:** Positive
**Covers:** 2.1 → Alert with the drop details; Rule: Alert events (sent, opened) 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: Alert with the drop details.
2. Observe the result and verify the full behavior: Alert with the drop details.
**Expected Result:** Alert with the drop details — delivered exactly as documented.
**Priority:** High

### TC-PT-7-02-005 — Link to the relevant report
**Type:** Positive
**Covers:** 2.1 → Link to the relevant report; Rule: The low performance alerts 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: Link to the relevant report.
2. Observe the result and verify the full behavior: Link to the relevant report.
**Expected Result:** Link to the relevant report — delivered exactly as documented.
**Priority:** High

### TC-PT-7-02-006 — Alert severity (warning, critical)
**Type:** Positive
**Covers:** 2.1 → Alert severity (warning, critical)
**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: Alert severity (warning.
2. Observe the result and verify the full behavior: Alert severity (warning, critical).
**Expected Result:** Alert severity (warning, critical) — delivered exactly as documented.
**Priority:** High

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

### TC-PT-7-02-008 — Audit logging of the low performance alerts
**Type:** Positive
**Covers:** 2.1 → Audit logging of the low performance alerts
**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 low performance alerts.
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 Missed Session Alerts

### TC-PT-7-02-009 — Alert on a missed live class
**Type:** Positive
**Covers:** 2.2 → Alert on a missed live class; Rule: Alerts are sent on missed sessions and deadlines.
**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: Alert on a missed live class.
2. Observe the result and verify the full behavior: Alert on a missed live class.
**Expected Result:** Alert on a missed live class — delivered exactly as documented.
**Priority:** Critical

### TC-PT-7-02-010 — Alert on a missed mandatory study session
**Type:** Edge
**Covers:** 2.2 → Alert on a missed mandatory study session; Rule: The alert includes the missed item and due time.
**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: Alert on a missed mandatory study session.
2. Observe the result and verify the full behavior: Alert on a missed mandatory study session.
**Expected Result:** Alert on a missed mandatory study session — delivered exactly as documented.
**Priority:** High

### TC-PT-7-02-011 — Alert on a missed assignment deadline
**Type:** Positive
**Covers:** 2.2 → Alert on a missed assignment deadline; Rule: A missed item detail opens on tap.
**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: Alert on a missed assignment deadline.
2. Observe the result and verify the full behavior: Alert on a missed assignment deadline.
**Expected Result:** Alert on a missed assignment deadline — delivered exactly as documented.
**Priority:** High

### TC-PT-7-02-012 — Alert with the missed item and due time
**Type:** Positive
**Covers:** 2.2 → Alert with the missed item and due time; Rule: Alert events (sent, opened) 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: Alert with the missed item and due time.
2. Observe the result and verify the full behavior: Alert with the missed item and due time.
**Expected Result:** Alert with the missed item and due time — delivered exactly as documented.
**Priority:** High

### TC-PT-7-02-013 — Missed item detail on tap
**Type:** Positive
**Covers:** 2.2 → Missed item detail on tap; Rule: The missed session alerts 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: Missed item detail on tap.
2. Observe the result and verify the full behavior: Missed item detail on tap.
**Expected Result:** Missed item detail on tap — delivered exactly as documented.
**Priority:** High

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

### TC-PT-7-02-015 — Audit logging of the missed session alerts
**Type:** Positive
**Covers:** 2.2 → Audit logging of the missed session alerts
**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 missed session alerts.
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 Engagement Drop Alerts

### TC-PT-7-02-016 — Alert on a significant decrease in study time
**Type:** Positive
**Covers:** 2.3 → Alert on a significant decrease in study time; Rule: Alerts are sent on significant engagement drops.
**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: Alert on a significant decrease in study time.
2. Observe the result and verify the full behavior: Alert on a significant decrease in study time.
**Expected Result:** Alert on a significant decrease in study time — delivered exactly as documented.
**Priority:** Critical

### TC-PT-7-02-017 — Alert on a break in the study streak
**Type:** Positive
**Covers:** 2.3 → Alert on a break in the study streak; Rule: The alert includes the engagement change.
**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: Alert on a break in the study streak.
2. Observe the result and verify the full behavior: Alert on a break in the study streak.
**Expected Result:** Alert on a break in the study streak — delivered exactly as documented.
**Priority:** High

### TC-PT-7-02-018 — Alert on inactivity for a defined period
**Type:** Positive
**Covers:** 2.3 → Alert on inactivity for a defined period; Rule: A link to the activity view is included.
**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: Alert on inactivity for a defined period.
2. Observe the result and verify the full behavior: Alert on inactivity for a defined period.
**Expected Result:** Alert on inactivity for a defined period — delivered exactly as documented.
**Priority:** High

### TC-PT-7-02-019 — Alert with the engagement change
**Type:** Positive
**Covers:** 2.3 → Alert with the engagement change; Rule: Alert events (sent, opened) 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: Alert with the engagement change.
2. Observe the result and verify the full behavior: Alert with the engagement change.
**Expected Result:** Alert with the engagement change — delivered exactly as documented.
**Priority:** High

### TC-PT-7-02-020 — Link to the activity view
**Type:** Positive
**Covers:** 2.3 → Link to the activity view; Rule: The engagement drop alerts 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: Link to the activity view.
2. Observe the result and verify the full behavior: Link to the activity view.
**Expected Result:** Link to the activity view — delivered exactly as documented.
**Priority:** High

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

### TC-PT-7-02-022 — Audit logging of the engagement drop alerts
**Type:** Positive
**Covers:** 2.3 → Audit logging of the engagement drop alerts
**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 engagement drop alerts.
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