# 3. Accountability Partners — Test Cases

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

## Test Execution Policy

- Zero tolerance: any deviation from the documented behavior is a defect.
- Every failed test is logged with a Bug ID, the feature, the sub-feature, the expected vs actual result, and the severity; 100% of bugs are fixed before the group passes.
- 100% pass rate is required for the group to be marked complete.

## Coverage Matrix

| Feature | Sub-feature / Rule | Test IDs |
|---------|--------------------|----------|
| 3.1 Partner Matching | Match criteria | TC-SA-VR-03-001 |
| 3.1 Partner Matching | Match creation | TC-SA-VR-03-002 |
| 3.1 Partner Matching | Match status | TC-SA-VR-03-003 |
| 3.1 Partner Matching | Match listing | TC-SA-VR-03-004 |
| 3.1 Partner Matching | Match history | TC-SA-VR-03-005 |
| 3.1 Partner Matching | Rule: a match without two learners cannot be created | TC-SA-VR-03-006 |
| 3.1 Partner Matching | Rule: match actions are audit-logged | TC-SA-VR-03-007 |
| 3.2 Goal Alignment | Goal link | TC-SA-VR-03-008 |
| 3.2 Goal Alignment | Goal comparison | TC-SA-VR-03-009 |
| 3.2 Goal Alignment | Goal sync | TC-SA-VR-03-010 |
| 3.2 Goal Alignment | Goal status | TC-SA-VR-03-011 |
| 3.2 Goal Alignment | Goal log | TC-SA-VR-03-012 |
| 3.2 Goal Alignment | Rule: a goal without a partner cannot be aligned | TC-SA-VR-03-013 |
| 3.2 Goal Alignment | Rule: goal actions are audit-logged | TC-SA-VR-03-014 |
| 3.3 Progress Check-ins | Check-in creation | TC-SA-VR-03-015 |
| 3.3 Progress Check-ins | Check-in frequency | TC-SA-VR-03-016 |
| 3.3 Progress Check-ins | Check-in status | TC-SA-VR-03-017 |
| 3.3 Progress Check-ins | Check-in log | TC-SA-VR-03-018 |
| 3.3 Progress Check-ins | Check-in history | TC-SA-VR-03-019 |
| 3.3 Progress Check-ins | Rule: a check-in without a partner cannot be created | TC-SA-VR-03-020 |
| 3.3 Progress Check-ins | Rule: check-in actions are audit-logged | TC-SA-VR-03-021 |
| 3.4 Friendly Competition | Competition creation | TC-SA-VR-03-022 |
| 3.4 Friendly Competition | Competition rules | TC-SA-VR-03-023 |
| 3.4 Friendly Competition | Competition leaderboard | TC-SA-VR-03-024 |
| 3.4 Friendly Competition | Competition status | TC-SA-VR-03-025 |
| 3.4 Friendly Competition | Competition log | TC-SA-VR-03-026 |
| 3.4 Friendly Competition | Rule: a competition without partners cannot be created | TC-SA-VR-03-027 |
| 3.4 Friendly Competition | Rule: competition actions are audit-logged | TC-SA-VR-03-028 |
| 3.5 Support Sessions | Support session creation | TC-SA-VR-03-029 |
| 3.5 Support Sessions | Support topic | TC-SA-VR-03-030 |
| 3.5 Support Sessions | Support status | TC-SA-VR-03-031 |
| 3.5 Support Sessions | Support log | TC-SA-VR-03-032 |
| 3.5 Support Sessions | Support history | TC-SA-VR-03-033 |
| 3.5 Support Sessions | Rule: a support session without partners cannot be created | TC-SA-VR-03-034 |
| 3.5 Support Sessions | Rule: support actions are audit-logged | TC-SA-VR-03-035 |

### TC-SA-VR-03-001 — Match criteria
**Type:** Positive
**Covers:** 3.1 → Match criteria: the criteria for the partner matching
**Preconditions:** A Super Admin account is active.
**Steps:**
1. As a Super Admin, set the match criteria and save.
2. Observe the result and verify the full behavior: the criteria are applied.
**Expected Result:** The criteria are set — they are applied, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-002 — Match creation
**Type:** Positive
**Covers:** 3.1 → Match creation: the creation of a partner match
**Preconditions:** A Super Admin account is active; two learners exist.
**Steps:**
1. As a Super Admin, create a partner match with two learners and save.
2. Observe the result and verify the full behavior: the match is created and listed.
**Expected Result:** The creation works — the match is listed, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-003 — Match status
**Type:** Positive
**Covers:** 3.1 → Match status: the status of the match
**Preconditions:** A Super Admin account is active; a match exists.
**Steps:**
1. As a Super Admin, view the match status.
2. Observe the result and verify the full behavior: the status is shown.
**Expected Result:** The status is shown — it reflects the state, delivered exactly as documented.
**Priority:** Medium

### TC-SA-VR-03-004 — Match listing
**Type:** Positive
**Covers:** 3.1 → Match listing: the listing of all matches
**Preconditions:** A Super Admin account is active; multiple matches exist.
**Steps:**
1. As a Super Admin, open the match listing.
2. Observe the result and verify the full behavior: all matches are listed.
**Expected Result:** The listing is shown — the matches are listed, delivered exactly as documented.
**Priority:** Low

### TC-SA-VR-03-005 — Match history
**Type:** Positive
**Covers:** 3.1 → Match history: the history of the matches
**Preconditions:** A Super Admin account is active; matches have a history.
**Steps:**
1. As a Super Admin, open the match history.
2. Observe the result and verify the full behavior: the past matches are listed.
**Expected Result:** The history is shown — the matches are listed, delivered exactly as documented.
**Priority:** Low

### TC-SA-VR-03-006 — Rule: a match without two learners cannot be created
**Type:** Negative
**Covers:** 3.1 → Rule: a match without two learners cannot be created
**Preconditions:** A Super Admin account is active; only one learner is selected.
**Steps:**
1. As a Super Admin, attempt to create the match with one learner.
2. Observe the result and verify the full behavior: the creation is blocked.
**Expected Result:** The creation is blocked — the two-learner precondition is enforced, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-007 — Rule: match actions are audit-logged
**Type:** Positive
**Covers:** 3.1 → Audit logging of partner matching
**Preconditions:** A Super Admin account is active; the audit log is accessible.
**Steps:**
1. As a Super Admin, create a match and save.
2. Open the audit log.
3. Observe the result and verify the full behavior: the action is recorded with the actor and timestamp.
**Expected Result:** The action is audit-logged — the actor and timestamp are recorded, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-008 — Goal link
**Type:** Positive
**Covers:** 3.2 → Goal link: the link of the partners' goals
**Preconditions:** A Super Admin account is active; a match exists with goals.
**Steps:**
1. As a Super Admin, link the partners' goals and save.
2. Observe the result and verify the full behavior: the goals are linked.
**Expected Result:** The link works — the goals are linked, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-009 — Goal comparison
**Type:** Positive
**Covers:** 3.2 → Goal comparison: the comparison of the goals
**Preconditions:** A Super Admin account is active; the goals are linked.
**Steps:**
1. As a Super Admin, view the goal comparison.
2. Observe the result and verify the full behavior: the differences are shown.
**Expected Result:** The comparison is shown — the differences are visible, delivered exactly as documented.
**Priority:** Medium

### TC-SA-VR-03-010 — Goal sync
**Type:** Positive
**Covers:** 3.2 → Goal sync: the synchronization of the goals
**Preconditions:** A Super Admin account is active; the goals are linked.
**Steps:**
1. As a Super Admin, sync the goals.
2. Observe the result and verify the full behavior: the goals are aligned.
**Expected Result:** The sync works — the goals are aligned, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-011 — Goal status
**Type:** Positive
**Covers:** 3.2 → Goal status: the status of the goal alignment
**Preconditions:** A Super Admin account is active; the goals are aligned.
**Steps:**
1. As a Super Admin, view the goal status.
2. Observe the result and verify the full behavior: the status is shown.
**Expected Result:** The status is shown — it reflects the state, delivered exactly as documented.
**Priority:** Low

### TC-SA-VR-03-012 — Goal log
**Type:** Positive
**Covers:** 3.2 → Goal log: the log of the goal alignment
**Preconditions:** A Super Admin account is active; goal alignment events exist.
**Steps:**
1. As a Super Admin, open the goal log.
2. Observe the result and verify the full behavior: the events are listed.
**Expected Result:** The log is shown — the events are listed, delivered exactly as documented.
**Priority:** Low

### TC-SA-VR-03-013 — Rule: a goal without a partner cannot be aligned
**Type:** Negative
**Covers:** 3.2 → Rule: a goal without a partner cannot be aligned
**Preconditions:** A Super Admin account is active; a goal has no partner.
**Steps:**
1. As a Super Admin, attempt to align the goal.
2. Observe the result and verify the full behavior: the alignment is blocked.
**Expected Result:** The alignment is blocked — the partner precondition is enforced, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-014 — Rule: goal actions are audit-logged
**Type:** Positive
**Covers:** 3.2 → Audit logging of goal alignment
**Preconditions:** A Super Admin account is active; the audit log is accessible.
**Steps:**
1. As a Super Admin, link the goals and save.
2. Open the audit log.
3. Observe the result and verify the full behavior: the action is recorded with the actor and timestamp.
**Expected Result:** The action is audit-logged — the actor and timestamp are recorded, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-015 — Check-in creation
**Type:** Positive
**Covers:** 3.3 → Check-in creation: the creation of a progress check-in
**Preconditions:** A Super Admin account is active; a match exists.
**Steps:**
1. As a Super Admin, create a progress check-in and save.
2. Observe the result and verify the full behavior: the check-in is created and listed.
**Expected Result:** The creation works — the check-in is listed, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-016 — Check-in frequency
**Type:** Positive
**Covers:** 3.3 → Check-in frequency: the frequency of the check-ins
**Preconditions:** A Super Admin account is active; a check-in exists.
**Steps:**
1. As a Super Admin, set the check-in frequency and save.
2. Observe the result and verify the full behavior: the frequency is applied.
**Expected Result:** The frequency is set — it is applied, delivered exactly as documented.
**Priority:** Medium

### TC-SA-VR-03-017 — Check-in status
**Type:** Positive
**Covers:** 3.3 → Check-in status: the status of the check-in
**Preconditions:** A Super Admin account is active; a check-in exists.
**Steps:**
1. As a Super Admin, view the check-in status.
2. Observe the result and verify the full behavior: the status is shown.
**Expected Result:** The status is shown — it reflects the state, delivered exactly as documented.
**Priority:** Medium

### TC-SA-VR-03-018 — Check-in log
**Type:** Positive
**Covers:** 3.3 → Check-in log: the log of the check-ins
**Preconditions:** A Super Admin account is active; check-ins exist.
**Steps:**
1. As a Super Admin, open the check-in log.
2. Observe the result and verify the full behavior: the check-ins are listed.
**Expected Result:** The log is shown — the check-ins are listed, delivered exactly as documented.
**Priority:** Low

### TC-SA-VR-03-019 — Check-in history
**Type:** Positive
**Covers:** 3.3 → Check-in history: the history of the check-ins
**Preconditions:** A Super Admin account is active; check-ins have a history.
**Steps:**
1. As a Super Admin, open the check-in history.
2. Observe the result and verify the full behavior: the past check-ins are listed.
**Expected Result:** The history is shown — the check-ins are listed, delivered exactly as documented.
**Priority:** Low

### TC-SA-VR-03-020 — Rule: a check-in without a partner cannot be created
**Type:** Negative
**Covers:** 3.3 → Rule: a check-in without a partner cannot be created
**Preconditions:** A Super Admin account is active; no partner is selected.
**Steps:**
1. As a Super Admin, attempt to create the check-in without a partner.
2. Observe the result and verify the full behavior: the creation is blocked.
**Expected Result:** The creation is blocked — the partner precondition is enforced, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-021 — Rule: check-in actions are audit-logged
**Type:** Positive
**Covers:** 3.3 → Audit logging of progress check-ins
**Preconditions:** A Super Admin account is active; the audit log is accessible.
**Steps:**
1. As a Super Admin, create a check-in and save.
2. Open the audit log.
3. Observe the result and verify the full behavior: the action is recorded with the actor and timestamp.
**Expected Result:** The action is audit-logged — the actor and timestamp are recorded, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-022 — Competition creation
**Type:** Positive
**Covers:** 3.4 → Competition creation: the creation of a friendly competition
**Preconditions:** A Super Admin account is active; partners exist.
**Steps:**
1. As a Super Admin, create a friendly competition and save.
2. Observe the result and verify the full behavior: the competition is created and listed.
**Expected Result:** The creation works — the competition is listed, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-023 — Competition rules
**Type:** Positive
**Covers:** 3.4 → Competition rules: the rules of the competition
**Preconditions:** A Super Admin account is active; a competition exists.
**Steps:**
1. As a Super Admin, set the competition rules and save.
2. Observe the result and verify the full behavior: the rules are applied.
**Expected Result:** The rules are set — they are applied, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-024 — Competition leaderboard
**Type:** Positive
**Covers:** 3.4 → Competition leaderboard: the leaderboard of the competition
**Preconditions:** A Super Admin account is active; a competition has scores.
**Steps:**
1. As a Super Admin, view the competition leaderboard.
2. Observe the result and verify the full behavior: the partners are ranked.
**Expected Result:** The leaderboard is shown — the partners are ranked, delivered exactly as documented.
**Priority:** Medium

### TC-SA-VR-03-025 — Competition status
**Type:** Positive
**Covers:** 3.4 → Competition status: the status of the competition
**Preconditions:** A Super Admin account is active; a competition exists.
**Steps:**
1. As a Super Admin, view the competition status.
2. Observe the result and verify the full behavior: the status is shown.
**Expected Result:** The status is shown — it reflects the state, delivered exactly as documented.
**Priority:** Low

### TC-SA-VR-03-026 — Competition log
**Type:** Positive
**Covers:** 3.4 → Competition log: the log of the competitions
**Preconditions:** A Super Admin account is active; competitions exist.
**Steps:**
1. As a Super Admin, open the competition log.
2. Observe the result and verify the full behavior: the competitions are listed.
**Expected Result:** The log is shown — the competitions are listed, delivered exactly as documented.
**Priority:** Low

### TC-SA-VR-03-027 — Rule: a competition without partners cannot be created
**Type:** Negative
**Covers:** 3.4 → Rule: a competition without partners cannot be created
**Preconditions:** A Super Admin account is active; no partners are selected.
**Steps:**
1. As a Super Admin, attempt to create the competition without partners.
2. Observe the result and verify the full behavior: the creation is blocked.
**Expected Result:** The creation is blocked — the partner precondition is enforced, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-028 — Rule: competition actions are audit-logged
**Type:** Positive
**Covers:** 3.4 → Audit logging of friendly competition
**Preconditions:** A Super Admin account is active; the audit log is accessible.
**Steps:**
1. As a Super Admin, create a competition and save.
2. Open the audit log.
3. Observe the result and verify the full behavior: the action is recorded with the actor and timestamp.
**Expected Result:** The action is audit-logged — the actor and timestamp are recorded, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-029 — Support session creation
**Type:** Positive
**Covers:** 3.5 → Support session creation: the creation of a support session
**Preconditions:** A Super Admin account is active; partners exist.
**Steps:**
1. As a Super Admin, create a support session and save.
2. Observe the result and verify the full behavior: the session is created and listed.
**Expected Result:** The creation works — the session is listed, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-030 — Support topic
**Type:** Positive
**Covers:** 3.5 → Support topic: the topic of the support session
**Preconditions:** A Super Admin account is active; a support session exists.
**Steps:**
1. As a Super Admin, set the support topic and save.
2. Observe the result and verify the full behavior: the topic is shown.
**Expected Result:** The topic is set — it is shown, delivered exactly as documented.
**Priority:** Medium

### TC-SA-VR-03-031 — Support status
**Type:** Positive
**Covers:** 3.5 → Support status: the status of the support session
**Preconditions:** A Super Admin account is active; a support session exists.
**Steps:**
1. As a Super Admin, view the support status.
2. Observe the result and verify the full behavior: the status is shown.
**Expected Result:** The status is shown — it reflects the state, delivered exactly as documented.
**Priority:** Low

### TC-SA-VR-03-032 — Support log
**Type:** Positive
**Covers:** 3.5 → Support log: the log of the support sessions
**Preconditions:** A Super Admin account is active; support sessions exist.
**Steps:**
1. As a Super Admin, open the support log.
2. Observe the result and verify the full behavior: the sessions are listed.
**Expected Result:** The log is shown — the sessions are listed, delivered exactly as documented.
**Priority:** Low

### TC-SA-VR-03-033 — Support history
**Type:** Positive
**Covers:** 3.5 → Support history: the history of the support sessions
**Preconditions:** A Super Admin account is active; support sessions have a history.
**Steps:**
1. As a Super Admin, open the support history.
2. Observe the result and verify the full behavior: the past sessions are listed.
**Expected Result:** The history is shown — the sessions are listed, delivered exactly as documented.
**Priority:** Low

### TC-SA-VR-03-034 — Rule: a support session without partners cannot be created
**Type:** Negative
**Covers:** 3.5 → Rule: a support session without partners cannot be created
**Preconditions:** A Super Admin account is active; no partners are selected.
**Steps:**
1. As a Super Admin, attempt to create the support session without partners.
2. Observe the result and verify the full behavior: the creation is blocked.
**Expected Result:** The creation is blocked — the partner precondition is enforced, delivered exactly as documented.
**Priority:** High

### TC-SA-VR-03-035 — Rule: support actions are audit-logged
**Type:** Positive
**Covers:** 3.5 → Audit logging of support sessions
**Preconditions:** A Super Admin account is active; the audit log is accessible.
**Steps:**
1. As a Super Admin, create a support session and save.
2. Open the audit log.
3. Observe the result and verify the full behavior: the action is recorded with the actor and timestamp.
**Expected Result:** The action is audit-logged — the actor and timestamp are recorded, delivered exactly as documented.
**Priority:** High