# 4. Mind Map Management — Test Cases

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*
Spec: mind_map_management.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 |
|---------|--------------------|----------|
| 4.1 Pre-Built Mind Maps for Each Topic | Pre-built mind map: the mind map created for a topic (the concepts and their relationships) | TC-SA-09-04-001 |
| 4.1 Pre-Built Mind Maps for Each Topic | Topic coverage: a mind map per topic (the topic's visual map) | TC-SA-09-04-002 |
| 4.1 Pre-Built Mind Maps for Each Topic | Concept nodes: the concepts as nodes, with the relationships between them | TC-SA-09-04-003 |
| 4.1 Pre-Built Mind Maps for Each Topic | Hierarchy: the topic's structure (the main concept, the sub-concepts) shown | TC-SA-09-04-004 |
| 4.1 Pre-Built Mind Maps for Each Topic | Visibility: the mind map shown in the topic's context | TC-SA-09-04-005 |
| 4.1 Pre-Built Mind Maps for Each Topic | Update: the mind map updated when the topic's content changes | TC-SA-09-04-006 |
| 4.1 Pre-Built Mind Maps for Each Topic | Audit logging of mind map create/update | TC-SA-09-04-007 |
| 4.1 Pre-Built Mind Maps for Each Topic | Rule: a mind map is per topic; it is the topic's visual map (the concepts and their relationships) | TC-SA-09-04-001 |
| 4.1 Pre-Built Mind Maps for Each Topic | Rule: the hierarchy is shown (the main concept, the sub-concepts); the structure is visible at a glance | TC-SA-09-04-004 |
| 4.1 Pre-Built Mind Maps for Each Topic | Rule: a content change (a concept added/revised) triggers a mind map update; the map matches the current content | TC-SA-09-04-006 |
| 4.1 Pre-Built Mind Maps for Each Topic | Rule: a topic missing its mind map is a visible gap; it is not a silent omission | TC-SA-09-04-008 |
| 4.1 Pre-Built Mind Maps for Each Topic | Rule: the mind map is a faithful representation (the concepts and relationships are correct); a wrong relationship is corrected | TC-SA-09-04-009 |
| 4.1 Pre-Built Mind Maps for Each Topic | Rule: mind map create/update is audit-logged with the topic, map, and timestamp | TC-SA-09-04-007 |
| 4.2 Interactive, Clickable Nodes | Clickable nodes: the nodes clickable (expand, collapse, or jump) | TC-SA-09-04-010 |
| 4.2 Interactive, Clickable Nodes | Expand/collapse: a node expanded to show its sub-concepts, or collapsed | TC-SA-09-04-011 |
| 4.2 Interactive, Clickable Nodes | Navigation: clicking a node navigates to the related content | TC-SA-09-04-012 |
| 4.2 Interactive, Clickable Nodes | Interactivity configuration: the interactivity set per mind map | TC-SA-09-04-013 |
| 4.2 Interactive, Clickable Nodes | Learner exploration: the learner explores the topic's structure by clicking | TC-SA-09-04-014 |
| 4.2 Interactive, Clickable Nodes | State: the learner's exploration state (the expanded/collapsed nodes) | TC-SA-09-04-015 |
| 4.2 Interactive, Clickable Nodes | Audit logging of interactivity configuration | TC-SA-09-04-016 |
| 4.2 Interactive, Clickable Nodes | Rule: the nodes are clickable; the interactivity is configured per mind map | TC-SA-09-04-013 |
| 4.2 Interactive, Clickable Nodes | Rule: the expand/collapse is learner-controlled (the depth is the learner's choice); the map is not forced to one view | TC-SA-09-04-011 |
| 4.2 Interactive, Clickable Nodes | Rule: the navigation (a node jumping to content) is set per node; a terminal node is non-navigable (it does not jump) | TC-SA-09-04-017 |
| 4.2 Interactive, Clickable Nodes | Rule: a node that should navigate but does not is a configuration issue; it is fixed | TC-SA-09-04-018 |
| 4.2 Interactive, Clickable Nodes | Rule: the learner's exploration state (the expanded/collapsed nodes) is the learner's; it is not reset arbitrarily | TC-SA-09-04-015 |
| 4.2 Interactive, Clickable Nodes | Rule: interactivity configuration is audit-logged with the mind map, configuration, and timestamp | TC-SA-09-04-016 |
| 4.3 Links to Related Videos/Resources and Color-Coding by Concept Importance | Content links: the nodes linked to the related videos/resources | TC-SA-09-04-019 |
| 4.3 Links to Related Videos/Resources and Color-Coding by Concept Importance | Link target: the video/resource for the concept (the content the node points to) | TC-SA-09-04-020 |
| 4.3 Links to Related Videos/Resources and Color-Coding by Concept Importance | Color-coding: the concepts color-coded by importance (core vs. supporting) | TC-SA-09-04-021 |
| 4.3 Links to Related Videos/Resources and Color-Coding by Concept Importance | Importance mapping: the color mapped to the concept's importance level | TC-SA-09-04-022 |
| 4.3 Links to Related Videos/Resources and Color-Coding by Concept Importance | Legend: the color meaning shown (the learner knows what the colors mean) | TC-SA-09-04-023 |
| 4.3 Links to Related Videos/Resources and Color-Coding by Concept Importance | Visibility: the links and colors shown in the mind map | TC-SA-09-04-024 |
| 4.3 Links to Related Videos/Resources and Color-Coding by Concept Importance | Audit logging of link/color-coding changes | TC-SA-09-04-025 |
| 4.3 Links to Related Videos/Resources and Color-Coding by Concept Importance | Rule: the content links connect the nodes to the related videos/resources; the map is a navigator to the content | TC-SA-09-04-019 |
| 4.3 Links to Related Videos/Resources and Color-Coding by Concept Importance | Rule: a node missing its content link is a gap (the content not attached); it is added or flagged | TC-SA-09-04-026 |
| 4.3 Links to Related Videos/Resources and Color-Coding by Concept Importance | Rule: the color-coding is by importance (the core vs. the supporting); the mapping is consistent | TC-SA-09-04-022 |
| 4.3 Links to Related Videos/Resources and Color-Coding by Concept Importance | Rule: the legend is shown; the learner knows what the colors mean (the colors are not arbitrary) | TC-SA-09-04-023 |
| 4.3 Links to Related Videos/Resources and Color-Coding by Concept Importance | Rule: a color-coding inconsistency (a core concept colored as supporting) is corrected; the change is recorded | TC-SA-09-04-027 |
| 4.3 Links to Related Videos/Resources and Color-Coding by Concept Importance | Rule: link/color-coding changes are audit-logged with the mind map, links, colors, and timestamp | TC-SA-09-04-025 |

## 4.1 Pre-Built Mind Maps for Each Topic

### TC-SA-09-04-001 — Pre-built mind map: the mind map created for a topic (the concepts and their relationships); it is per topic
**Type:** Positive
**Covers:** 4.1 → Pre-built mind map: the mind map created for a topic (the concepts and their relationships); Rule: a mind map is per topic; it is the topic's visual map (the concepts and their relationships)
**Preconditions:** A topic exists; the topic's concepts and relationships are mapped.
**Steps:**
1. For the topic, create the pre-built mind map: the topic's concepts as nodes, with the relationships between them.
2. Save and verify the mind map is available for the topic.
**Expected Result:** The pre-built mind map is created — the topic's visual map (the concepts and their relationships), per topic.
**Priority:** Critical

### TC-SA-09-04-002 — Topic coverage: a mind map per topic (the topic's visual map)
**Type:** Positive
**Covers:** 4.1 → Topic coverage: a mind map per topic (the topic's visual map)
**Preconditions:** Multiple topics exist; mind maps are created for each.
**Steps:**
1. Review the topic coverage: the topics with their mind maps.
2. Verify a mind map exists per topic (the topic's visual map).
**Expected Result:** A mind map exists per topic — the topic's visual map.
**Priority:** High

### TC-SA-09-04-003 — Concept nodes: the concepts as nodes, with the relationships between them
**Type:** Positive
**Covers:** 4.1 → Concept nodes: the concepts as nodes, with the relationships between them
**Preconditions:** A topic's mind map is created.
**Steps:**
1. Review the mind map: verify the concepts are represented as nodes.
2. Verify the relationships between the concepts are shown (the connections between the nodes).
**Expected Result:** The concepts are nodes, with the relationships between them shown.
**Priority:** High

### TC-SA-09-04-004 — Hierarchy: the topic's structure (the main concept, the sub-concepts) shown; the structure is visible at a glance
**Type:** Positive
**Covers:** 4.1 → Hierarchy: the topic's structure (the main concept, the sub-concepts) shown; Rule: the hierarchy is shown (the main concept, the sub-concepts); the structure is visible at a glance
**Preconditions:** A topic's mind map is created.
**Steps:**
1. Review the mind map: verify the hierarchy is shown (the main concept, the sub-concepts).
2. Verify the structure is visible at a glance.
**Expected Result:** The hierarchy is shown (the main concept, the sub-concepts) — the structure is visible at a glance.
**Priority:** High

### TC-SA-09-04-005 — Visibility: the mind map shown in the topic's context
**Type:** Positive
**Covers:** 4.1 → Visibility: the mind map shown in the topic's context
**Preconditions:** A topic has a mind map.
**Steps:**
1. As a learner, open the topic's context.
2. Verify the mind map is shown in the topic's context (the learner sees the topic's visual map where the topic is taught).
**Expected Result:** The mind map is shown in the topic's context.
**Priority:** High

### TC-SA-09-04-006 — Update: the mind map updated when the topic's content changes; the map matches the current content
**Type:** Negative
**Covers:** 4.1 → Update: the mind map updated when the topic's content changes; Rule: a content change (a concept added/revised) triggers a mind map update; the map matches the current content
**Preconditions:** A topic's content changes (a concept added/revised); the mind map is now out of date.
**Steps:**
1. Update the topic's content (a concept added/revised).
2. Verify the mind map is updated to match.
3. Verify the map matches the current content.
**Expected Result:** The mind map is updated when the topic's content changes — the map matches the current content.
**Priority:** Critical

### TC-SA-09-04-007 — Mind map create/update is audit-logged with the topic, the map, and the timestamp
**Type:** Positive
**Covers:** 4.1 → Audit logging of mind map create/update; Rule: mind map create/update is audit-logged with the topic, map, and timestamp
**Preconditions:** Mind map create/update events have occurred.
**Steps:**
1. Open the audit trail and filter by "mind map".
2. Verify entries for create/update show the topic, the map, and the timestamp.
**Expected Result:** The mind map create/update is audit-logged with the topic, map, and timestamp.
**Priority:** Critical

### TC-SA-09-04-008 — A topic missing its mind map is a visible gap; it is not a silent omission
**Type:** Negative
**Covers:** 4.1 → Rule: a topic missing its mind map is a visible gap; it is not a silent omission
**Preconditions:** A topic has no mind map.
**Steps:**
1. Review the topic coverage: the topics with their mind maps.
2. Verify the topic missing its mind map is a visible gap (flagged in the coverage view).
3. Verify it is not a silent omission.
**Expected Result:** The topic missing its mind map is a visible gap — it is not a silent omission.
**Priority:** High

### TC-SA-09-04-009 — The mind map is a faithful representation (the concepts and relationships are correct); a wrong relationship is corrected
**Type:** Negative
**Covers:** 4.1 → Rule: the mind map is a faithful representation (the concepts and relationships are correct); a wrong relationship is corrected
**Preconditions:** A mind map has a wrong relationship (a connection between two concepts that is incorrect).
**Steps:**
1. Review the mind map: verify the concepts and relationships are correct.
2. Identify the wrong relationship.
3. Correct it and verify the change is recorded.
**Expected Result:** The mind map is a faithful representation — the wrong relationship is corrected.
**Priority:** Critical

## 4.2 Interactive, Clickable Nodes

### TC-SA-09-04-010 — Clickable nodes: the nodes clickable (expand, collapse, or jump)
**Type:** Positive
**Covers:** 4.2 → Clickable nodes: the nodes clickable (expand, collapse, or jump)
**Preconditions:** A topic's mind map is created with interactive nodes.
**Steps:**
1. As a learner, open the mind map.
2. Click a node and verify it responds (expand, collapse, or jump).
**Expected Result:** The nodes are clickable — they respond to clicks (expand, collapse, or jump).
**Priority:** High

### TC-SA-09-04-011 — Expand/collapse: a node expanded to show its sub-concepts, or collapsed; the depth is the learner's choice
**Type:** Positive
**Covers:** 4.2 → Expand/collapse: a node expanded to show its sub-concepts, or collapsed; Rule: the expand/collapse is learner-controlled (the depth is the learner's choice); the map is not forced to one view
**Preconditions:** A topic's mind map has nodes with sub-concepts.
**Steps:**
1. As the learner, expand a node and verify its sub-concepts are shown.
2. Collapse the node and verify the sub-concepts are hidden.
3. Verify the depth is the learner's choice (the map is not forced to one view).
**Expected Result:** The expand/collapse is learner-controlled — the depth is the learner's choice; the map is not forced to one view.
**Priority:** High

### TC-SA-09-04-012 — Navigation: clicking a node navigates to the related content
**Type:** Positive
**Covers:** 4.2 → Navigation: clicking a node navigates to the related content
**Preconditions:** A mind map node is configured to navigate to related content.
**Steps:**
1. As the learner, click the node.
2. Verify it navigates to the related content.
**Expected Result:** Clicking the node navigates to the related content.
**Priority:** High

### TC-SA-09-04-013 — Interactivity configuration: the interactivity set per mind map; the nodes are clickable
**Type:** Positive
**Covers:** 4.2 → Interactivity configuration: the interactivity set per mind map; Rule: the nodes are clickable; the interactivity is configured per mind map
**Preconditions:** A topic's mind map is created.
**Steps:**
1. Configure the interactivity for the mind map: which nodes are clickable, what each does (expand, collapse, jump).
2. Verify the interactivity is set per mind map.
**Expected Result:** The interactivity is configured per mind map — the nodes are clickable as configured.
**Priority:** High

### TC-SA-09-04-014 — Learner exploration: the learner explores the topic's structure by clicking
**Type:** Positive
**Covers:** 4.2 → Learner exploration: the learner explores the topic's structure by clicking
**Preconditions:** A topic's mind map is interactive.
**Steps:**
1. As the learner, explore the topic's structure by clicking through the nodes.
2. Verify the learner can explore the topic's structure by clicking.
**Expected Result:** The learner explores the topic's structure by clicking.
**Priority:** Medium

### TC-SA-09-04-015 — State: the learner's exploration state (the expanded/collapsed nodes) is the learner's; it is not reset arbitrarily
**Type:** Negative
**Covers:** 4.2 → State: the learner's exploration state (the expanded/collapsed nodes); Rule: the learner's exploration state (the expanded/collapsed nodes) is the learner's; it is not reset arbitrarily
**Preconditions:** A learner has expanded/collapsed nodes in a mind map.
**Steps:**
1. As the learner, expand/collapse several nodes.
2. Leave and return to the mind map.
3. Verify the learner's exploration state (the expanded/collapsed nodes) is preserved (it is the learner's, not reset arbitrarily).
**Expected Result:** The learner's exploration state is preserved — it is the learner's, not reset arbitrarily.
**Priority:** High

### TC-SA-09-04-016 — Interactivity configuration is audit-logged with the mind map, the configuration, and the timestamp
**Type:** Positive
**Covers:** 4.2 → Audit logging of interactivity configuration; Rule: interactivity configuration is audit-logged with the mind map, configuration, and timestamp
**Preconditions:** Interactivity configuration changes have occurred.
**Steps:**
1. Open the audit trail and filter by "mind map interactivity".
2. Verify entries show the mind map, the configuration, and the timestamp.
**Expected Result:** The interactivity configuration is audit-logged with the mind map, configuration, and timestamp.
**Priority:** Critical

### TC-SA-09-04-017 — The navigation (a node jumping to content) is set per node; a terminal node is non-navigable (it does not jump)
**Type:** Edge
**Covers:** 4.2 → Rule: the navigation (a node jumping to content) is set per node; a terminal node is non-navigable (it does not jump)
**Preconditions:** A mind map has navigable nodes and terminal nodes.
**Steps:**
1. Click a navigable node and verify it jumps to the content.
2. Click a terminal node and verify it does not jump (it is non-navigable).
**Expected Result:** The navigation is set per node — a terminal node is non-navigable (it does not jump).
**Priority:** Medium

### TC-SA-09-04-018 — A node that should navigate but does not is a configuration issue; it is fixed
**Type:** Negative
**Covers:** 4.2 → Rule: a node that should navigate but does not is a configuration issue; it is fixed
**Preconditions:** A node is configured to navigate but does not (a broken navigation).
**Steps:**
1. Click the node and verify it does not navigate (the configuration issue).
2. Fix the configuration (set the correct navigation target).
3. Verify the node now navigates correctly.
**Expected Result:** The node that should navigate but does not is a configuration issue — it is fixed.
**Priority:** Critical

## 4.3 Links to Related Videos/Resources and Color-Coding by Concept Importance

### TC-SA-09-04-019 — Content links: the nodes linked to the related videos/resources; the map is a navigator to the content
**Type:** Positive
**Covers:** 4.3 → Content links: the nodes linked to the related videos/resources; Rule: the content links connect the nodes to the related videos/resources; the map is a navigator to the content
**Preconditions:** A topic's mind map is created; related videos/resources exist.
**Steps:**
1. For the mind map, link the nodes to the related videos/resources (the content for each concept).
2. Verify the content links connect the nodes to the related videos/resources.
**Expected Result:** The content links connect the nodes to the related videos/resources — the map is a navigator to the content.
**Priority:** High

### TC-SA-09-04-020 — Link target: the video/resource for the concept (the content the node points to)
**Type:** Positive
**Covers:** 4.3 → Link target: the video/resource for the concept (the content the node points to)
**Preconditions:** A mind map node is linked to content.
**Steps:**
1. Review the node's link target: verify it is the video/resource for the concept (the content the node points to).
2. Click the link and verify it opens the correct content.
**Expected Result:** The link target is the video/resource for the concept — the content the node points to.
**Priority:** High

### TC-SA-09-04-021 — Color-coding: the concepts color-coded by importance (core vs. supporting)
**Type:** Positive
**Covers:** 4.3 → Color-coding: the concepts color-coded by importance (core vs. supporting)
**Preconditions:** A topic's mind map is created.
**Steps:**
1. Color-code the concepts by importance: the core concepts vs. the supporting concepts.
2. Verify the color-coding is applied.
**Expected Result:** The concepts are color-coded by importance (core vs. supporting).
**Priority:** High

### TC-SA-09-04-022 — Importance mapping: the color mapped to the concept's importance level; the mapping is consistent
**Type:** Negative
**Covers:** 4.3 → Importance mapping: the color mapped to the concept's importance level; Rule: the color-coding is by importance (the core vs. the supporting); the mapping is consistent
**Preconditions:** A mind map has color-coding by importance.
**Steps:**
1. Review the importance mapping: verify the color is mapped to the concept's importance level.
2. Verify the mapping is consistent (the same importance level always has the same color).
**Expected Result:** The color is mapped to the concept's importance level — the mapping is consistent.
**Priority:** High

### TC-SA-09-04-023 — Legend: the color meaning shown (the learner knows what the colors mean); the colors are not arbitrary
**Type:** Positive
**Covers:** 4.3 → Legend: the color meaning shown (the learner knows what the colors mean); Rule: the legend is shown; the learner knows what the colors mean (the colors are not arbitrary)
**Preconditions:** A mind map has color-coding by importance.
**Steps:**
1. As the learner, open the mind map.
2. Verify the legend is shown (the color meaning).
3. Verify the learner knows what the colors mean (the colors are not arbitrary).
**Expected Result:** The legend is shown — the learner knows what the colors mean (the colors are not arbitrary).
**Priority:** High

### TC-SA-09-04-024 — Visibility: the links and colors shown in the mind map
**Type:** Positive
**Covers:** 4.3 → Visibility: the links and colors shown in the mind map
**Preconditions:** A mind map has content links and color-coding.
**Steps:**
1. As the learner, open the mind map.
2. Verify the links and colors are shown in the mind map.
**Expected Result:** The links and colors are shown in the mind map.
**Priority:** Medium

### TC-SA-09-04-025 — Link/color-coding changes are audit-logged with the mind map, the links, the colors, and the timestamp
**Type:** Positive
**Covers:** 4.3 → Audit logging of link/color-coding changes; Rule: link/color-coding changes are audit-logged with the mind map, links, colors, and timestamp
**Preconditions:** Link/color-coding changes have occurred.
**Steps:**
1. Open the audit trail and filter by "mind map links/colors".
2. Verify entries show the mind map, the links, the colors, and the timestamp.
**Expected Result:** The link/color-coding changes are audit-logged with the mind map, links, colors, and timestamp.
**Priority:** Critical

### TC-SA-09-04-026 — A node missing its content link is a gap (the content not attached); it is added or flagged
**Type:** Negative
**Covers:** 4.3 → Rule: a node missing its content link is a gap (the content not attached); it is added or flagged
**Preconditions:** A mind map node has no content link (the content is not attached).
**Steps:**
1. Review the mind map: identify the node missing its content link.
2. Add the content link (or flag the gap).
3. Verify the gap is resolved or flagged.
**Expected Result:** The node missing its content link is a gap — it is added or flagged.
**Priority:** High

### TC-SA-09-04-027 — A color-coding inconsistency (a core concept colored as supporting) is corrected; the change is recorded
**Type:** Negative
**Covers:** 4.3 → Rule: a color-coding inconsistency (a core concept colored as supporting) is corrected; the change is recorded
**Preconditions:** A core concept is colored as supporting (a color-coding inconsistency).
**Steps:**
1. Review the color-coding: identify the inconsistency (a core concept colored as supporting).
2. Correct it (recolor the concept as core).
3. Verify the change is recorded.
**Expected Result:** The color-coding inconsistency is corrected — the change is recorded.
**Priority:** Critical