# 7. Platform Integrations — Test Cases

User Type: **Organization**
Source: *Mi Digital Academy - Education CRM Features Document*
Spec: platform_integrations.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 |
|---------|--------------------|----------|
| 7.1 | LMS connection setup and configuration | TC-ORG-7-01-001 |
| 7.1 | Course sync from LMS | TC-ORG-7-01-002 |
| 7.1 | User sync from LMS | TC-ORG-7-01-003 |
| 7.1 | Progress sync to LMS | TC-ORG-7-01-004 |
| 7.1 | Sync status and error log | TC-ORG-7-01-005 |
| 7.1 | Government LMS Integration available on web and mobile | TC-ORG-7-01-006 |
| 7.1 | government lms integration event logging (viewed) | TC-ORG-7-01-007 |
| 7.1 | Audit logging of government lms integration | TC-ORG-7-01-008 |
| 7.1 | Rule: LMS connection setup and configuration. | TC-ORG-7-01-009 |
| 7.1 | Rule: Course sync from LMS. | TC-ORG-7-01-010 |
| 7.1 | Rule: User sync from LMS. | TC-ORG-7-01-011 |
| 7.1 | Rule: Progress sync to LMS. | TC-ORG-7-01-012 |
| 7.1 | Rule: Sync status and error log. | TC-ORG-7-01-013 |
| 7.2 | Scheduled data sync | TC-ORG-7-02-014 |
| 7.2 | On-demand data sync | TC-ORG-7-02-015 |
| 7.2 | Sync scope selection (users, programs, results) | TC-ORG-7-02-016 |
| 7.2 | Conflict detection and handling | TC-ORG-7-02-017 |
| 7.2 | Sync history and status | TC-ORG-7-02-018 |
| 7.2 | Data Sync available on web and mobile | TC-ORG-7-02-019 |
| 7.2 | data sync event logging (viewed) | TC-ORG-7-02-020 |
| 7.2 | Audit logging of data sync | TC-ORG-7-02-021 |
| 7.2 | Rule: Scheduled data sync. | TC-ORG-7-02-022 |
| 7.2 | Rule: On-demand data sync. | TC-ORG-7-02-023 |
| 7.2 | Rule: Sync scope selection (users, programs, results). | TC-ORG-7-02-024 |
| 7.2 | Rule: Conflict detection and handling. | TC-ORG-7-02-025 |
| 7.2 | Rule: Sync history and status. | TC-ORG-7-02-026 |

## 7.1 Government LMS Integration

### TC-ORG-7-01-001 — LMS connection setup and configuration
**Type:** Positive
**Covers:** 7.1 → LMS connection setup and configuration; Rule: LMS connection setup and configuration.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: LMS connection setup and configuration.
2. Observe the result and verify the full behavior: LMS connection setup and configuration.
**Expected Result:** LMS connection setup and configuration — delivered exactly as documented.
**Priority:** Critical

### TC-ORG-7-01-002 — Course sync from LMS
**Type:** Positive
**Covers:** 7.1 → Course sync from LMS; Rule: Course sync from LMS.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: Course sync from LMS.
2. Observe the result and verify the full behavior: Course sync from LMS.
**Expected Result:** Course sync from LMS — delivered exactly as documented.
**Priority:** High

### TC-ORG-7-01-003 — User sync from LMS
**Type:** Positive
**Covers:** 7.1 → User sync from LMS; Rule: User sync from LMS.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: User sync from LMS.
2. Observe the result and verify the full behavior: User sync from LMS.
**Expected Result:** User sync from LMS — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-01-004 — Progress sync to LMS
**Type:** Positive
**Covers:** 7.1 → Progress sync to LMS; Rule: Progress sync to LMS.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: Progress sync to LMS.
2. Observe the result and verify the full behavior: Progress sync to LMS.
**Expected Result:** Progress sync to LMS — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-01-005 — Sync status and error log
**Type:** Positive
**Covers:** 7.1 → Sync status and error log; Rule: Sync status and error log.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: Sync status and error log.
2. Observe the result and verify the full behavior: Sync status and error log.
**Expected Result:** Sync status and error log — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-01-006 — Government LMS Integration available on web and mobile
**Type:** Positive
**Covers:** 7.1 → Government LMS Integration available on web and mobile; Rule: LMS connection setup and configuration.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: Government LMS Integration available on web and mobile.
2. Observe the result and verify the full behavior: Government LMS Integration available on web and mobile.
**Expected Result:** Government LMS Integration available on web and mobile — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-01-007 — government lms integration event logging (viewed)
**Type:** Positive
**Covers:** 7.1 → government lms integration event logging (viewed); Rule: Course sync from LMS.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: government lms integration event logging (viewed).
2. Observe the result and verify the full behavior: government lms integration event logging (viewed).
**Expected Result:** government lms integration event logging (viewed) — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-01-008 — Audit logging of government lms integration
**Type:** Positive
**Covers:** 7.1 → Audit logging of government lms integration; Rule: User sync from LMS.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: Audit logging of government lms integration.
2. Observe the result and verify the full behavior: Audit logging of government lms integration.
**Expected Result:** Audit logging of government lms integration — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-01-009 — Rule: LMS connection setup and configuration.
**Type:** Positive
**Covers:** 7.1 → Rule: LMS connection setup and configuration.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform the action that triggers the rule: LMS connection setup and configuration.
2. Observe the result and verify the full behavior: LMS connection setup and configuration.
**Expected Result:** LMS connection setup and configuration. — delivered exactly as documented.
**Priority:** Critical

### TC-ORG-7-01-010 — Rule: Course sync from LMS.
**Type:** Positive
**Covers:** 7.1 → Rule: Course sync from LMS.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform the action that triggers the rule: Course sync from LMS.
2. Observe the result and verify the full behavior: Course sync from LMS.
**Expected Result:** Course sync from LMS. — delivered exactly as documented.
**Priority:** High

### TC-ORG-7-01-011 — Rule: User sync from LMS.
**Type:** Positive
**Covers:** 7.1 → Rule: User sync from LMS.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform the action that triggers the rule: User sync from LMS.
2. Observe the result and verify the full behavior: User sync from LMS.
**Expected Result:** User sync from LMS. — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-01-012 — Rule: Progress sync to LMS.
**Type:** Positive
**Covers:** 7.1 → Rule: Progress sync to LMS.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform the action that triggers the rule: Progress sync to LMS.
2. Observe the result and verify the full behavior: Progress sync to LMS.
**Expected Result:** Progress sync to LMS. — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-01-013 — Rule: Sync status and error log.
**Type:** Positive
**Covers:** 7.1 → Rule: Sync status and error log.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform the action that triggers the rule: Sync status and error log.
2. Observe the result and verify the full behavior: Sync status and error log.
**Expected Result:** Sync status and error log. — delivered exactly as documented.
**Priority:** Medium

## 7.2 Data Sync

### TC-ORG-7-02-014 — Scheduled data sync
**Type:** Positive
**Covers:** 7.2 → Scheduled data sync; Rule: Scheduled data sync.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: Scheduled data sync.
2. Observe the result and verify the full behavior: Scheduled data sync.
**Expected Result:** Scheduled data sync — delivered exactly as documented.
**Priority:** Critical

### TC-ORG-7-02-015 — On-demand data sync
**Type:** Positive
**Covers:** 7.2 → On-demand data sync; Rule: On-demand data sync.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: On-demand data sync.
2. Observe the result and verify the full behavior: On-demand data sync.
**Expected Result:** On-demand data sync — delivered exactly as documented.
**Priority:** High

### TC-ORG-7-02-016 — Sync scope selection (users, programs, results)
**Type:** Positive
**Covers:** 7.2 → Sync scope selection (users, programs, results); Rule: Sync scope selection (users, programs, results).
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: Sync scope selection (users, programs, results).
2. Observe the result and verify the full behavior: Sync scope selection (users, programs, results).
**Expected Result:** Sync scope selection (users, programs, results) — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-02-017 — Conflict detection and handling
**Type:** Positive
**Covers:** 7.2 → Conflict detection and handling; Rule: Conflict detection and handling.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: Conflict detection and handling.
2. Observe the result and verify the full behavior: Conflict detection and handling.
**Expected Result:** Conflict detection and handling — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-02-018 — Sync history and status
**Type:** Positive
**Covers:** 7.2 → Sync history and status; Rule: Sync history and status.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: Sync history and status.
2. Observe the result and verify the full behavior: Sync history and status.
**Expected Result:** Sync history and status — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-02-019 — Data Sync available on web and mobile
**Type:** Positive
**Covers:** 7.2 → Data Sync available on web and mobile; Rule: Scheduled data sync.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: Data Sync available on web and mobile.
2. Observe the result and verify the full behavior: Data Sync available on web and mobile.
**Expected Result:** Data Sync available on web and mobile — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-02-020 — data sync event logging (viewed)
**Type:** Positive
**Covers:** 7.2 → data sync event logging (viewed); Rule: On-demand data sync.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: data sync event logging (viewed).
2. Observe the result and verify the full behavior: data sync event logging (viewed).
**Expected Result:** data sync event logging (viewed) — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-02-021 — Audit logging of data sync
**Type:** Positive
**Covers:** 7.2 → Audit logging of data sync; Rule: Sync scope selection (users, programs, results).
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform: Audit logging of data sync.
2. Observe the result and verify the full behavior: Audit logging of data sync.
**Expected Result:** Audit logging of data sync — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-02-022 — Rule: Scheduled data sync.
**Type:** Positive
**Covers:** 7.2 → Rule: Scheduled data sync.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform the action that triggers the rule: Scheduled data sync.
2. Observe the result and verify the full behavior: Scheduled data sync.
**Expected Result:** Scheduled data sync. — delivered exactly as documented.
**Priority:** Critical

### TC-ORG-7-02-023 — Rule: On-demand data sync.
**Type:** Positive
**Covers:** 7.2 → Rule: On-demand data sync.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform the action that triggers the rule: On-demand data sync.
2. Observe the result and verify the full behavior: On-demand data sync.
**Expected Result:** On-demand data sync. — delivered exactly as documented.
**Priority:** High

### TC-ORG-7-02-024 — Rule: Sync scope selection (users, programs, results).
**Type:** Positive
**Covers:** 7.2 → Rule: Sync scope selection (users, programs, results).
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform the action that triggers the rule: Sync scope selection (users, programs, results).
2. Observe the result and verify the full behavior: Sync scope selection (users, programs, results).
**Expected Result:** Sync scope selection (users, programs, results). — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-02-025 — Rule: Conflict detection and handling.
**Type:** Positive
**Covers:** 7.2 → Rule: Conflict detection and handling.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform the action that triggers the rule: Conflict detection and handling.
2. Observe the result and verify the full behavior: Conflict detection and handling.
**Expected Result:** Conflict detection and handling. — delivered exactly as documented.
**Priority:** Medium

### TC-ORG-7-02-026 — Rule: Sync history and status.
**Type:** Positive
**Covers:** 7.2 → Rule: Sync history and status.
**Preconditions:** A Organization account is active and the Organization is in the state required for this behavior.
**Steps:**
1. As a Organization, set up the precondition and perform the action that triggers the rule: Sync history and status.
2. Observe the result and verify the full behavior: Sync history and status.
**Expected Result:** Sync history and status. — delivered exactly as documented.
**Priority:** Medium