# 2. Performance Analytics — Test Cases

User Type: **Student**
Source: *Mi Digital Academy - Education CRM Features Document*
Spec: performance_analytics.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 Performance Dashboard | Performance dashboard with scores across subjects | TC-ST-08-02-001 |
| 2.1 Performance Dashboard | Accuracy trends over time | TC-ST-08-02-002 |
| 2.1 Performance Dashboard | Overall performance summary | TC-ST-08-02-003 |
| 2.1 Performance Dashboard | Highlight top and weak subjects | TC-ST-08-02-004 |
| 2.1 Performance Dashboard | Dashboard per subject and overall | TC-ST-08-02-005 |
| 2.1 Performance Dashboard | Dashboard available on web and mobile | TC-ST-08-02-006 |
| 2.1 Performance Dashboard | Dashboard event logging (viewed) | TC-ST-08-02-007 |
| 2.1 Performance Dashboard | Audit logging of the performance dashboard | TC-ST-08-02-008 |
| 2.1 Performance Dashboard | Rule: The dashboard aggregates the Student's assessment and practice performance. | TC-ST-08-02-001 |
| 2.1 Performance Dashboard | Rule: Accuracy trends are computed over the selected period. | TC-ST-08-02-002 |
| 2.1 Performance Dashboard | Rule: Top and weak subjects are highlighted. | TC-ST-08-02-003 |
| 2.1 Performance Dashboard | Rule: The dashboard is available per subject and overall. | TC-ST-08-02-004 |
| 2.1 Performance Dashboard | Rule: Dashboard events (viewed) are logged with the timestamp. | TC-ST-08-02-005 |
| 2.1 Performance Dashboard | Rule: The performance dashboard is audit-logged with the account and the timestamp. | TC-ST-08-02-006 |
| 2.2 Strengths and Weaknesses Analysis | Strengths identified by subject and topic | TC-ST-08-02-009 |
| 2.2 Strengths and Weaknesses Analysis | Weaknesses identified by subject and topic | TC-ST-08-02-010 |
| 2.2 Strengths and Weaknesses Analysis | Analysis based on assessment accuracy and practice performance | TC-ST-08-02-011 |
| 2.2 Strengths and Weaknesses Analysis | Mastery levels per topic | TC-ST-08-02-012 |
| 2.2 Strengths and Weaknesses Analysis | "Focus on" list of weak topics | TC-ST-08-02-013 |
| 2.2 Strengths and Weaknesses Analysis | "Maintain" list of strong topics | TC-ST-08-02-014 |
| 2.2 Strengths and Weaknesses Analysis | Analysis updates as performance changes | TC-ST-08-02-015 |
| 2.2 Strengths and Weaknesses Analysis | Analysis event logging (computed) | TC-ST-08-02-016 |
| 2.2 Strengths and Weaknesses Analysis | Audit logging of the strengths and weaknesses analysis | TC-ST-08-02-017 |
| 2.2 Strengths and Weaknesses Analysis | Rule: Strengths and weaknesses are derived from assessment accuracy and practice performance. | TC-ST-08-02-009 |
| 2.2 Strengths and Weaknesses Analysis | Rule: A topic is a weakness when its accuracy is below the threshold. | TC-ST-08-02-010 |
| 2.2 Strengths and Weaknesses Analysis | Rule: The "Focus on" and "Maintain" lists are derived from the analysis. | TC-ST-08-02-011 |
| 2.2 Strengths and Weaknesses Analysis | Rule: The analysis updates as performance changes. | TC-ST-08-02-012 |
| 2.2 Strengths and Weaknesses Analysis | Rule: Analysis events (computed) are logged with the timestamp. | TC-ST-08-02-013 |
| 2.2 Strengths and Weaknesses Analysis | Rule: The strengths and weaknesses analysis is audit-logged with the account and the timestamp. | TC-ST-08-02-014 |
| 2.3 Benchmark Comparison | Comparison against grade-level benchmarks | TC-ST-08-02-018 |
| 2.3 Benchmark Comparison | Benchmark per subject | TC-ST-08-02-019 |
| 2.3 Benchmark Comparison | Student's percentile vs the benchmark | TC-ST-08-02-020 |
| 2.3 Benchmark Comparison | Gap to the benchmark shown | TC-ST-08-02-021 |
| 2.3 Benchmark Comparison | Benchmark updates as the Student improves | TC-ST-08-02-022 |
| 2.3 Benchmark Comparison | Benchmark available on web and mobile | TC-ST-08-02-023 |
| 2.3 Benchmark Comparison | Benchmark event logging (viewed) | TC-ST-08-02-024 |
| 2.3 Benchmark Comparison | Audit logging of the benchmark comparison | TC-ST-08-02-025 |
| 2.3 Benchmark Comparison | Rule: The benchmark is grade-level and per subject. | TC-ST-08-02-018 |
| 2.3 Benchmark Comparison | Rule: The Student's percentile is computed against the benchmark. | TC-ST-08-02-019 |
| 2.3 Benchmark Comparison | Rule: The gap to the benchmark is shown. | TC-ST-08-02-020 |
| 2.3 Benchmark Comparison | Rule: The comparison updates as the Student improves. | TC-ST-08-02-021 |
| 2.3 Benchmark Comparison | Rule: Benchmark events (viewed) are logged with the subject and the timestamp. | TC-ST-08-02-022 |
| 2.3 Benchmark Comparison | Rule: The benchmark comparison is audit-logged with the account, the subject, and the timestamp. | TC-ST-08-02-023 |

## 2.1 Performance Dashboard

### TC-ST-08-02-001 — Performance dashboard with scores across subjects
**Type:** Positive
**Covers:** 2.1 → Performance dashboard with scores across subjects; Rule: The dashboard aggregates the Student's assessment and practice performance.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Performance dashboard with scores across subjects.
2. Observe the result and verify the full behavior: Performance dashboard with scores across subjects.
**Expected Result:** Performance dashboard with scores across subjects — delivered exactly as documented.
**Priority:** Critical

### TC-ST-08-02-002 — Accuracy trends over time
**Type:** Positive
**Covers:** 2.1 → Accuracy trends over time; Rule: Accuracy trends are computed over the selected period.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Accuracy trends over time.
2. Observe the result and verify the full behavior: Accuracy trends over time.
**Expected Result:** Accuracy trends over time — delivered exactly as documented.
**Priority:** High

### TC-ST-08-02-003 — Overall performance summary
**Type:** Positive
**Covers:** 2.1 → Overall performance summary; Rule: Top and weak subjects are highlighted.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Overall performance summary.
2. Observe the result and verify the full behavior: Overall performance summary.
**Expected Result:** Overall performance summary — delivered exactly as documented.
**Priority:** High

### TC-ST-08-02-004 — Highlight top and weak subjects
**Type:** Edge
**Covers:** 2.1 → Highlight top and weak subjects; Rule: The dashboard is available per subject and overall.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Highlight top and weak subjects.
2. Observe the result and verify the full behavior: Highlight top and weak subjects.
**Expected Result:** Highlight top and weak subjects — delivered exactly as documented.
**Priority:** High

### TC-ST-08-02-005 — Dashboard per subject and overall
**Type:** Positive
**Covers:** 2.1 → Dashboard per subject and overall; Rule: Dashboard events (viewed) are logged with the timestamp.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Dashboard per subject and overall.
2. Observe the result and verify the full behavior: Dashboard per subject and overall.
**Expected Result:** Dashboard per subject and overall — delivered exactly as documented.
**Priority:** High

### TC-ST-08-02-006 — Dashboard available on web and mobile
**Type:** Positive
**Covers:** 2.1 → Dashboard available on web and mobile; Rule: The performance dashboard is audit-logged with the account and the timestamp.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Dashboard available on web and mobile.
2. Observe the result and verify the full behavior: Dashboard available on web and mobile.
**Expected Result:** Dashboard available on web and mobile — delivered exactly as documented.
**Priority:** High

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

### TC-ST-08-02-008 — Audit logging of the performance dashboard
**Type:** Positive
**Covers:** 2.1 → Audit logging of the performance dashboard
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, perform the action associated with: Audit logging of the performance dashboard.
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 Strengths and Weaknesses Analysis

### TC-ST-08-02-009 — Strengths identified by subject and topic
**Type:** Edge
**Covers:** 2.2 → Strengths identified by subject and topic; Rule: Strengths and weaknesses are derived from assessment accuracy and practice performance.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Strengths identified by subject and topic.
2. Observe the result and verify the full behavior: Strengths identified by subject and topic.
**Expected Result:** Strengths identified by subject and topic — delivered exactly as documented.
**Priority:** Critical

### TC-ST-08-02-010 — Weaknesses identified by subject and topic
**Type:** Edge
**Covers:** 2.2 → Weaknesses identified by subject and topic; Rule: A topic is a weakness when its accuracy is below the threshold.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Weaknesses identified by subject and topic.
2. Observe the result and verify the full behavior: Weaknesses identified by subject and topic.
**Expected Result:** Weaknesses identified by subject and topic — delivered exactly as documented.
**Priority:** High

### TC-ST-08-02-011 — Analysis based on assessment accuracy and practice performance
**Type:** Positive
**Covers:** 2.2 → Analysis based on assessment accuracy and practice performance; Rule: The "Focus on" and "Maintain" lists are derived from the analysis.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Analysis based on assessment accuracy and practice performance.
2. Observe the result and verify the full behavior: Analysis based on assessment accuracy and practice performance.
**Expected Result:** Analysis based on assessment accuracy and practice performance — delivered exactly as documented.
**Priority:** High

### TC-ST-08-02-012 — Mastery levels per topic
**Type:** Positive
**Covers:** 2.2 → Mastery levels per topic; Rule: The analysis updates as performance changes.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Mastery levels per topic.
2. Observe the result and verify the full behavior: Mastery levels per topic.
**Expected Result:** Mastery levels per topic — delivered exactly as documented.
**Priority:** High

### TC-ST-08-02-013 — "Focus on" list of weak topics
**Type:** Edge
**Covers:** 2.2 → "Focus on" list of weak topics; Rule: Analysis events (computed) are logged with the timestamp.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: "Focus on" list of weak topics.
2. Observe the result and verify the full behavior: "Focus on" list of weak topics.
**Expected Result:** "Focus on" list of weak topics — delivered exactly as documented.
**Priority:** High

### TC-ST-08-02-014 — "Maintain" list of strong topics
**Type:** Positive
**Covers:** 2.2 → "Maintain" list of strong topics; Rule: The strengths and weaknesses analysis is audit-logged with the account and the timestamp.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: "Maintain" list of strong topics.
2. Observe the result and verify the full behavior: "Maintain" list of strong topics.
**Expected Result:** "Maintain" list of strong topics — delivered exactly as documented.
**Priority:** High

### TC-ST-08-02-015 — Analysis updates as performance changes
**Type:** Positive
**Covers:** 2.2 → Analysis updates as performance changes
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Analysis updates as performance changes.
2. Observe the result and verify the full behavior: Analysis updates as performance changes.
**Expected Result:** Analysis updates as performance changes — delivered exactly as documented.
**Priority:** High

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

### TC-ST-08-02-017 — Audit logging of the strengths and weaknesses analysis
**Type:** Edge
**Covers:** 2.2 → Audit logging of the strengths and weaknesses analysis
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, 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.3 Benchmark Comparison

### TC-ST-08-02-018 — Comparison against grade-level benchmarks
**Type:** Positive
**Covers:** 2.3 → Comparison against grade-level benchmarks; Rule: The benchmark is grade-level and per subject.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Comparison against grade-level benchmarks.
2. Observe the result and verify the full behavior: Comparison against grade-level benchmarks.
**Expected Result:** Comparison against grade-level benchmarks — delivered exactly as documented.
**Priority:** Critical

### TC-ST-08-02-019 — Benchmark per subject
**Type:** Positive
**Covers:** 2.3 → Benchmark per subject; Rule: The Student's percentile is computed against the benchmark.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Benchmark per subject.
2. Observe the result and verify the full behavior: Benchmark per subject.
**Expected Result:** Benchmark per subject — delivered exactly as documented.
**Priority:** High

### TC-ST-08-02-020 — Student's percentile vs the benchmark
**Type:** Positive
**Covers:** 2.3 → Student's percentile vs the benchmark; Rule: The gap to the benchmark is shown.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Student's percentile vs the benchmark.
2. Observe the result and verify the full behavior: Student's percentile vs the benchmark.
**Expected Result:** Student's percentile vs the benchmark — delivered exactly as documented.
**Priority:** High

### TC-ST-08-02-021 — Gap to the benchmark shown
**Type:** Positive
**Covers:** 2.3 → Gap to the benchmark shown; Rule: The comparison updates as the Student improves.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Gap to the benchmark shown.
2. Observe the result and verify the full behavior: Gap to the benchmark shown.
**Expected Result:** Gap to the benchmark shown — delivered exactly as documented.
**Priority:** High

### TC-ST-08-02-022 — Benchmark updates as the Student improves
**Type:** Positive
**Covers:** 2.3 → Benchmark updates as the Student improves; Rule: Benchmark events (viewed) are logged with the subject and the timestamp.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, set up the precondition and perform: Benchmark updates as the Student improves.
2. Observe the result and verify the full behavior: Benchmark updates as the Student improves.
**Expected Result:** Benchmark updates as the Student improves — delivered exactly as documented.
**Priority:** High

### TC-ST-08-02-023 — Benchmark available on web and mobile
**Type:** Positive
**Covers:** 2.3 → Benchmark available on web and mobile; Rule: The benchmark comparison is audit-logged with the account, the subject, and the timestamp.
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, 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-ST-08-02-024 — Benchmark event logging (viewed)
**Type:** Positive
**Covers:** 2.3 → Benchmark event logging (viewed)
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, 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-ST-08-02-025 — Audit logging of the benchmark comparison
**Type:** Positive
**Covers:** 2.3 → Audit logging of the benchmark comparison
**Preconditions:** A Student account is active and the Student is in the state required for this behavior.
**Steps:**
1. As a Student, perform the action associated with: Audit logging of the 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