# 2. Strengths, Weaknesses & Benchmarks — Test Cases

User Type: **Parent**
Source: *Mi Digital Academy - Education CRM Features Document*
Spec: strengths_weaknesses_benchmarks.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 Strengths and Weaknesses Analysis | Strengths and weaknesses across subjects | TC-PT-4-02-001 |
| 2.1 Strengths and Weaknesses Analysis | Topic-level strength/weakness breakdown | TC-PT-4-02-002 |
| 2.1 Strengths and Weaknesses Analysis | Recommendations to improve weak areas | TC-PT-4-02-003 |
| 2.1 Strengths and Weaknesses Analysis | Trend of strengths/weaknesses over time | TC-PT-4-02-004 |
| 2.1 Strengths and Weaknesses Analysis | Analysis available on web and mobile | TC-PT-4-02-005 |
| 2.1 Strengths and Weaknesses Analysis | Analysis event logging (viewed) | TC-PT-4-02-006 |
| 2.1 Strengths and Weaknesses Analysis | Audit logging of the strengths and weaknesses analysis | TC-PT-4-02-007 |
| 2.1 Strengths and Weaknesses Analysis | Rule: The analysis is based on the child's performance data. | TC-PT-4-02-001 |
| 2.1 Strengths and Weaknesses Analysis | Rule: The breakdown is at the subject and topic level. | TC-PT-4-02-002 |
| 2.1 Strengths and Weaknesses Analysis | Rule: Recommendations target the weak areas. | TC-PT-4-02-003 |
| 2.1 Strengths and Weaknesses Analysis | Rule: Analysis events (viewed) are logged with the account and the timestamp. | TC-PT-4-02-004 |
| 2.1 Strengths and Weaknesses Analysis | Rule: The strengths and weaknesses analysis is audit-logged with the account and the timestamp. | TC-PT-4-02-005 |
| 2.2 Grade-Level Benchmark Comparison | Comparison with grade-level benchmarks | TC-PT-4-02-008 |
| 2.2 Grade-Level Benchmark Comparison | Benchmark by subject | TC-PT-4-02-009 |
| 2.2 Grade-Level Benchmark Comparison | Child's percentile vs grade average | TC-PT-4-02-010 |
| 2.2 Grade-Level Benchmark Comparison | Above/below benchmark indicator | TC-PT-4-02-011 |
| 2.2 Grade-Level Benchmark Comparison | Benchmark period selection | TC-PT-4-02-012 |
| 2.2 Grade-Level Benchmark Comparison | Benchmark available on web and mobile | TC-PT-4-02-013 |
| 2.2 Grade-Level Benchmark Comparison | Benchmark event logging (viewed) | TC-PT-4-02-014 |
| 2.2 Grade-Level Benchmark Comparison | Audit logging of the grade-level benchmark comparison | TC-PT-4-02-015 |
| 2.2 Grade-Level Benchmark Comparison | Rule: The comparison is against grade-level benchmarks. | TC-PT-4-02-008 |
| 2.2 Grade-Level Benchmark Comparison | Rule: The benchmark is by subject. | TC-PT-4-02-009 |
| 2.2 Grade-Level Benchmark Comparison | Rule: Benchmark events (viewed) are logged with the account and the timestamp. | TC-PT-4-02-010 |
| 2.2 Grade-Level Benchmark Comparison | Rule: The grade-level benchmark comparison is audit-logged with the account and the timestamp. | TC-PT-4-02-011 |
| 2.3 Learning Pattern Insights | Peak performance times | TC-PT-4-02-016 |
| 2.3 Learning Pattern Insights | Best study days | TC-PT-4-02-017 |
| 2.3 Learning Pattern Insights | Performance under different conditions | TC-PT-4-02-018 |
| 2.3 Learning Pattern Insights | Learning pattern summary | TC-PT-4-02-019 |
| 2.3 Learning Pattern Insights | Pattern trend over time | TC-PT-4-02-020 |
| 2.3 Learning Pattern Insights | Insights available on web and mobile | TC-PT-4-02-021 |
| 2.3 Learning Pattern Insights | Insight event logging (viewed) | TC-PT-4-02-022 |
| 2.3 Learning Pattern Insights | Audit logging of the learning pattern insights | TC-PT-4-02-023 |
| 2.3 Learning Pattern Insights | Rule: The insights are based on the child's activity and performance data. | TC-PT-4-02-016 |
| 2.3 Learning Pattern Insights | Rule: The peak performance times are identified. | TC-PT-4-02-017 |
| 2.3 Learning Pattern Insights | Rule: Insight events (viewed) are logged with the account and the timestamp. | TC-PT-4-02-018 |
| 2.3 Learning Pattern Insights | Rule: The learning pattern insights is audit-logged with the account and the timestamp. | TC-PT-4-02-019 |

## 2.1 Strengths and Weaknesses Analysis

### TC-PT-4-02-001 — Strengths and weaknesses across subjects
**Type:** Edge
**Covers:** 2.1 → Strengths and weaknesses across subjects; Rule: The analysis is based on the child's performance data.
**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: Strengths and weaknesses across subjects.
2. Observe the result and verify the full behavior: Strengths and weaknesses across subjects.
**Expected Result:** Strengths and weaknesses across subjects — delivered exactly as documented.
**Priority:** Critical

### TC-PT-4-02-002 — Topic-level strength/weakness breakdown
**Type:** Edge
**Covers:** 2.1 → Topic-level strength/weakness breakdown; Rule: The breakdown is at the subject and topic level.
**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: Topic-level strength/weakness breakdown.
2. Observe the result and verify the full behavior: Topic-level strength/weakness breakdown.
**Expected Result:** Topic-level strength/weakness breakdown — delivered exactly as documented.
**Priority:** High

### TC-PT-4-02-003 — Recommendations to improve weak areas
**Type:** Edge
**Covers:** 2.1 → Recommendations to improve weak areas; Rule: Recommendations target the weak areas.
**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: Recommendations to improve weak areas.
2. Observe the result and verify the full behavior: Recommendations to improve weak areas.
**Expected Result:** Recommendations to improve weak areas — delivered exactly as documented.
**Priority:** High

### TC-PT-4-02-004 — Trend of strengths/weaknesses over time
**Type:** Edge
**Covers:** 2.1 → Trend of strengths/weaknesses over time; Rule: Analysis events (viewed) 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: Trend of strengths/weaknesses over time.
2. Observe the result and verify the full behavior: Trend of strengths/weaknesses over time.
**Expected Result:** Trend of strengths/weaknesses over time — delivered exactly as documented.
**Priority:** High

### TC-PT-4-02-005 — Analysis available on web and mobile
**Type:** Positive
**Covers:** 2.1 → Analysis available on web and mobile; Rule: The strengths and weaknesses analysis 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: Analysis available on web and mobile.
2. Observe the result and verify the full behavior: Analysis available on web and mobile.
**Expected Result:** Analysis available on web and mobile — delivered exactly as documented.
**Priority:** High

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

### TC-PT-4-02-007 — Audit logging of the strengths and weaknesses analysis
**Type:** Edge
**Covers:** 2.1 → Audit logging of the strengths and weaknesses analysis
**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 strengths and weaknesses analysis.
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 Grade-Level Benchmark Comparison

### TC-PT-4-02-008 — Comparison with grade-level benchmarks
**Type:** Positive
**Covers:** 2.2 → Comparison with grade-level benchmarks; Rule: The comparison is against grade-level benchmarks.
**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: Comparison with grade-level benchmarks.
2. Observe the result and verify the full behavior: Comparison with grade-level benchmarks.
**Expected Result:** Comparison with grade-level benchmarks — delivered exactly as documented.
**Priority:** Critical

### TC-PT-4-02-009 — Benchmark by subject
**Type:** Positive
**Covers:** 2.2 → Benchmark by subject; Rule: The benchmark is by subject.
**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: Benchmark by subject.
2. Observe the result and verify the full behavior: Benchmark by subject.
**Expected Result:** Benchmark by subject — delivered exactly as documented.
**Priority:** High

### TC-PT-4-02-010 — Child's percentile vs grade average
**Type:** Positive
**Covers:** 2.2 → Child's percentile vs grade average; Rule: Benchmark events (viewed) 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: Child's percentile vs grade average.
2. Observe the result and verify the full behavior: Child's percentile vs grade average.
**Expected Result:** Child's percentile vs grade average — delivered exactly as documented.
**Priority:** High

### TC-PT-4-02-011 — Above/below benchmark indicator
**Type:** Positive
**Covers:** 2.2 → Above/below benchmark indicator; Rule: The grade-level benchmark comparison 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: Above/below benchmark indicator.
2. Observe the result and verify the full behavior: Above/below benchmark indicator.
**Expected Result:** Above/below benchmark indicator — delivered exactly as documented.
**Priority:** High

### TC-PT-4-02-012 — Benchmark period selection
**Type:** Positive
**Covers:** 2.2 → Benchmark period selection
**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: Benchmark period selection.
2. Observe the result and verify the full behavior: Benchmark period selection.
**Expected Result:** Benchmark period selection — delivered exactly as documented.
**Priority:** High

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

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

### TC-PT-4-02-015 — Audit logging of the grade-level benchmark comparison
**Type:** Positive
**Covers:** 2.2 → Audit logging of the grade-level benchmark comparison
**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 grade-level benchmark comparison.
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 Learning Pattern Insights

### TC-PT-4-02-016 — Peak performance times
**Type:** Positive
**Covers:** 2.3 → Peak performance times; Rule: The insights are based on the child's activity and performance data.
**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: Peak performance times.
2. Observe the result and verify the full behavior: Peak performance times.
**Expected Result:** Peak performance times — delivered exactly as documented.
**Priority:** Critical

### TC-PT-4-02-017 — Best study days
**Type:** Positive
**Covers:** 2.3 → Best study days; Rule: The peak performance times are identified.
**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: Best study days.
2. Observe the result and verify the full behavior: Best study days.
**Expected Result:** Best study days — delivered exactly as documented.
**Priority:** High

### TC-PT-4-02-018 — Performance under different conditions
**Type:** Positive
**Covers:** 2.3 → Performance under different conditions; Rule: Insight events (viewed) 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: Performance under different conditions.
2. Observe the result and verify the full behavior: Performance under different conditions.
**Expected Result:** Performance under different conditions — delivered exactly as documented.
**Priority:** High

### TC-PT-4-02-019 — Learning pattern summary
**Type:** Positive
**Covers:** 2.3 → Learning pattern summary; Rule: The learning pattern insights 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: Learning pattern summary.
2. Observe the result and verify the full behavior: Learning pattern summary.
**Expected Result:** Learning pattern summary — delivered exactly as documented.
**Priority:** High

### TC-PT-4-02-020 — Pattern trend over time
**Type:** Positive
**Covers:** 2.3 → Pattern trend over 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: Pattern trend over time.
2. Observe the result and verify the full behavior: Pattern trend over time.
**Expected Result:** Pattern trend over time — delivered exactly as documented.
**Priority:** High

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

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

### TC-PT-4-02-023 — Audit logging of the learning pattern insights
**Type:** Positive
**Covers:** 2.3 → Audit logging of the learning pattern insights
**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 learning pattern insights.
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