# 3.3 Department Grouping — Test Cases

User Type: **Corporate**
Source: *Mi Digital Academy - Education CRM Features Document*
Spec: department_grouping.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.3.1 | Create a department (name, description, manager) | TC-COR-3-03-001 |
| 3.3.1 | Rename and edit departments | TC-COR-3-03-002 |
| 3.3.1 | Merge two departments | TC-COR-3-03-003 |
| 3.3.1 | Archive a department | TC-COR-3-03-004 |
| 3.3.1 | Available on web and mobile | TC-COR-3-03-005 |
| 3.3.1 | Event logging (viewed) | TC-COR-3-03-006 |
| 3.3.1 | Audit logging of the department management | TC-COR-3-03-007 |
| 3.3.1 | Rule: A department with employees cannot be deleted, only archived after emptying. | TC-COR-3-03-008 |
| 3.3.1 | Rule: Merging keeps all learning and compliance records on the employees. | TC-COR-3-03-009 |
| 3.3.1 | Rule: Department names are unique within the account. | TC-COR-3-03-010 |
| 3.3.1 | Rule: Events (viewed) are logged with the account and the timestamp. | TC-COR-3-03-011 |
| 3.3.1 | Rule: The department management is audit-logged with the account and the timestamp. | TC-COR-3-03-012 |
| 3.3.2 | Assign an employee to a department | TC-COR-3-03-013 |
| 3.3.2 | Bulk reassignment (multi-select) | TC-COR-3-03-014 |
| 3.3.2 | One primary department per employee | TC-COR-3-03-015 |
| 3.3.2 | Reassignment history | TC-COR-3-03-016 |
| 3.3.2 | Available on web and mobile | TC-COR-3-03-017 |
| 3.3.2 | Event logging (viewed) | TC-COR-3-03-018 |
| 3.3.2 | Audit logging of the employee department assignment | TC-COR-3-03-019 |
| 3.3.2 | Rule: Each employee has exactly one primary department. | TC-COR-3-03-020 |
| 3.3.2 | Rule: Moving an employee does not change their learning records. | TC-COR-3-03-021 |
| 3.3.2 | Rule: Events (viewed) are logged with the account and the timestamp. | TC-COR-3-03-022 |
| 3.3.2 | Rule: The employee department assignment is audit-logged with the account and the timestamp. | TC-COR-3-03-023 |
| 3.3.3 | Create a team within a department | TC-COR-3-03-024 |
| 3.3.3 | Assign employees to teams | TC-COR-3-03-025 |
| 3.3.3 | Team-level assignment targeting | TC-COR-3-03-026 |
| 3.3.3 | Team roster view | TC-COR-3-03-027 |
| 3.3.3 | Available on web and mobile | TC-COR-3-03-028 |
| 3.3.3 | Event logging (viewed) | TC-COR-3-03-029 |
| 3.3.3 | Audit logging of the nested teams | TC-COR-3-03-030 |
| 3.3.3 | Rule: A team belongs to exactly one department. | TC-COR-3-03-031 |
| 3.3.3 | Rule: An employee can belong to multiple teams but one primary department. | TC-COR-3-03-032 |
| 3.3.3 | Rule: Events (viewed) are logged with the account and the timestamp. | TC-COR-3-03-033 |
| 3.3.3 | Rule: The nested teams are audit-logged with the account and the timestamp. | TC-COR-3-03-034 |


## 3.3.1 Create & Manage Departments

### TC-COR-3-03-001 — Create a department (name, description, manager)

**Type:** Positive

**Covers:** 3.3.1 → Create a department (name, description, manager); Rule: A department with employees cannot be deleted, only archived after emptying.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Create a department (name, description, manager).

2. Observe the result and verify the full behavior: Create a department (name, description, manager).

**Expected Result:** Create a department (name, description, manager) — delivered exactly as documented.

**Priority:** Critical

### TC-COR-3-03-002 — Rename and edit departments

**Type:** Positive

**Covers:** 3.3.1 → Rename and edit departments; Rule: A department with employees cannot be deleted, only archived after emptying.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Rename and edit departments.

2. Observe the result and verify the full behavior: Rename and edit departments.

**Expected Result:** Rename and edit departments — delivered exactly as documented.

**Priority:** Critical

### TC-COR-3-03-003 — Merge two departments

**Type:** Positive

**Covers:** 3.3.1 → Merge two departments; Rule: A department with employees cannot be deleted, only archived after emptying.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Merge two departments.

2. Observe the result and verify the full behavior: Merge two departments.

**Expected Result:** Merge two departments — delivered exactly as documented.

**Priority:** Critical

### TC-COR-3-03-004 — Archive a department

**Type:** Positive

**Covers:** 3.3.1 → Archive a department; Rule: A department with employees cannot be deleted, only archived after emptying.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Archive a department.

2. Observe the result and verify the full behavior: Archive a department.

**Expected Result:** Archive a department — delivered exactly as documented.

**Priority:** Critical

### TC-COR-3-03-005 — Available on web and mobile

**Type:** Positive

**Covers:** 3.3.1 → Available on web and mobile; Rule: A department with employees cannot be deleted, only archived after emptying.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Available on web and mobile.

2. Observe the result and verify the full behavior: Available on web and mobile.

**Expected Result:** Available on web and mobile — delivered exactly as documented.

**Priority:** Critical

### TC-COR-3-03-006 — Event logging (viewed)

**Type:** Positive

**Covers:** 3.3.1 → Event logging (viewed); Rule: A department with employees cannot be deleted, only archived after emptying.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Event logging (viewed).

2. Observe the result and verify the full behavior: Event logging (viewed).

**Expected Result:** Event logging (viewed) — delivered exactly as documented.

**Priority:** Medium

### TC-COR-3-03-007 — Audit logging of the department management

**Type:** Positive

**Covers:** 3.3.1 → Audit logging of the department management; Rule: A department with employees cannot be deleted, only archived after emptying.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Audit logging of the department management.

2. Observe the result and verify the full behavior: Audit logging of the department management.

**Expected Result:** Audit logging of the department management — delivered exactly as documented.

**Priority:** Medium

### TC-COR-3-03-008 — Rule: A department with employees cannot be deleted, only archived after emptying.

**Type:** Positive

**Covers:** 3.3.1 → A department with employees cannot be deleted, only archived after emptying.; Rule: A department with employees cannot be deleted, only archived after emptying..

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: A department with employees cannot be deleted, only archived after emptying..

2. Observe the result and verify the full behavior: A department with employees cannot be deleted, only archived after emptying..

**Expected Result:** A department with employees cannot be deleted, only archived after emptying. — delivered exactly as documented.

**Priority:** High

### TC-COR-3-03-009 — Rule: Merging keeps all learning and compliance records on the employees.

**Type:** Positive

**Covers:** 3.3.1 → Merging keeps all learning and compliance records on the employees.; Rule: Merging keeps all learning and compliance records on the employees..

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Merging keeps all learning and compliance records on the employees..

2. Observe the result and verify the full behavior: Merging keeps all learning and compliance records on the employees..

**Expected Result:** Merging keeps all learning and compliance records on the employees. — delivered exactly as documented.

**Priority:** High

### TC-COR-3-03-010 — Rule: Department names are unique within the account.

**Type:** Positive

**Covers:** 3.3.1 → Department names are unique within the account.; Rule: Department names are unique within the account..

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Department names are unique within the account..

2. Observe the result and verify the full behavior: Department names are unique within the account..

**Expected Result:** Department names are unique within the account. — delivered exactly as documented.

**Priority:** High

### TC-COR-3-03-011 — Rule: Events (viewed) are logged with the account and the timestamp.

**Type:** Positive

**Covers:** 3.3.1 → Events (viewed) are logged with the account and the timestamp.; Rule: Events (viewed) are logged with the account and the timestamp..

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Events (viewed) are logged with the account and the timestamp..

2. Observe the result and verify the full behavior: Events (viewed) are logged with the account and the timestamp..

**Expected Result:** Events (viewed) are logged with the account and the timestamp. — delivered exactly as documented.

**Priority:** High

### TC-COR-3-03-012 — Rule: The department management is audit-logged with the account and the timestamp.

**Type:** Positive

**Covers:** 3.3.1 → The department management is audit-logged with the account and the timestamp.; Rule: The department management is audit-logged with the account and the timestamp..

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: The department management is audit-logged with the account and the timestamp..

2. Observe the result and verify the full behavior: The department management is audit-logged with the account and the timestamp..

**Expected Result:** The department management is audit-logged with the account and the timestamp. — delivered exactly as documented.

**Priority:** High


## 3.3.2 Assign Employees to Departments

### TC-COR-3-03-013 — Assign an employee to a department

**Type:** Positive

**Covers:** 3.3.2 → Assign an employee to a department; Rule: Each employee has exactly one primary department.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Assign an employee to a department.

2. Observe the result and verify the full behavior: Assign an employee to a department.

**Expected Result:** Assign an employee to a department — delivered exactly as documented.

**Priority:** Critical

### TC-COR-3-03-014 — Bulk reassignment (multi-select)

**Type:** Positive

**Covers:** 3.3.2 → Bulk reassignment (multi-select); Rule: Each employee has exactly one primary department.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Bulk reassignment (multi-select).

2. Observe the result and verify the full behavior: Bulk reassignment (multi-select).

**Expected Result:** Bulk reassignment (multi-select) — delivered exactly as documented.

**Priority:** Critical

### TC-COR-3-03-015 — One primary department per employee

**Type:** Positive

**Covers:** 3.3.2 → One primary department per employee; Rule: Each employee has exactly one primary department.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: One primary department per employee.

2. Observe the result and verify the full behavior: One primary department per employee.

**Expected Result:** One primary department per employee — delivered exactly as documented.

**Priority:** Critical

### TC-COR-3-03-016 — Reassignment history

**Type:** Positive

**Covers:** 3.3.2 → Reassignment history; Rule: Each employee has exactly one primary department.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Reassignment history.

2. Observe the result and verify the full behavior: Reassignment history.

**Expected Result:** Reassignment history — delivered exactly as documented.

**Priority:** Critical

### TC-COR-3-03-017 — Available on web and mobile

**Type:** Positive

**Covers:** 3.3.2 → Available on web and mobile; Rule: Each employee has exactly one primary department.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Available on web and mobile.

2. Observe the result and verify the full behavior: Available on web and mobile.

**Expected Result:** Available on web and mobile — delivered exactly as documented.

**Priority:** Critical

### TC-COR-3-03-018 — Event logging (viewed)

**Type:** Positive

**Covers:** 3.3.2 → Event logging (viewed); Rule: Each employee has exactly one primary department.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Event logging (viewed).

2. Observe the result and verify the full behavior: Event logging (viewed).

**Expected Result:** Event logging (viewed) — delivered exactly as documented.

**Priority:** Medium

### TC-COR-3-03-019 — Audit logging of the employee department assignment

**Type:** Positive

**Covers:** 3.3.2 → Audit logging of the employee department assignment; Rule: Each employee has exactly one primary department.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Audit logging of the employee department assignment.

2. Observe the result and verify the full behavior: Audit logging of the employee department assignment.

**Expected Result:** Audit logging of the employee department assignment — delivered exactly as documented.

**Priority:** Medium

### TC-COR-3-03-020 — Rule: Each employee has exactly one primary department.

**Type:** Positive

**Covers:** 3.3.2 → Each employee has exactly one primary department.; Rule: Each employee has exactly one primary department..

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Each employee has exactly one primary department..

2. Observe the result and verify the full behavior: Each employee has exactly one primary department..

**Expected Result:** Each employee has exactly one primary department. — delivered exactly as documented.

**Priority:** High

### TC-COR-3-03-021 — Rule: Moving an employee does not change their learning records.

**Type:** Positive

**Covers:** 3.3.2 → Moving an employee does not change their learning records.; Rule: Moving an employee does not change their learning records..

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Moving an employee does not change their learning records..

2. Observe the result and verify the full behavior: Moving an employee does not change their learning records..

**Expected Result:** Moving an employee does not change their learning records. — delivered exactly as documented.

**Priority:** High

### TC-COR-3-03-022 — Rule: Events (viewed) are logged with the account and the timestamp.

**Type:** Positive

**Covers:** 3.3.2 → Events (viewed) are logged with the account and the timestamp.; Rule: Events (viewed) are logged with the account and the timestamp..

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Events (viewed) are logged with the account and the timestamp..

2. Observe the result and verify the full behavior: Events (viewed) are logged with the account and the timestamp..

**Expected Result:** Events (viewed) are logged with the account and the timestamp. — delivered exactly as documented.

**Priority:** High

### TC-COR-3-03-023 — Rule: The employee department assignment is audit-logged with the account and the timestamp.

**Type:** Positive

**Covers:** 3.3.2 → The employee department assignment is audit-logged with the account and the timestamp.; Rule: The employee department assignment is audit-logged with the account and the timestamp..

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: The employee department assignment is audit-logged with the account and the timestamp..

2. Observe the result and verify the full behavior: The employee department assignment is audit-logged with the account and the timestamp..

**Expected Result:** The employee department assignment is audit-logged with the account and the timestamp. — delivered exactly as documented.

**Priority:** High


## 3.3.3 Nested Teams

### TC-COR-3-03-024 — Create a team within a department

**Type:** Positive

**Covers:** 3.3.3 → Create a team within a department; Rule: A team belongs to exactly one department.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Create a team within a department.

2. Observe the result and verify the full behavior: Create a team within a department.

**Expected Result:** Create a team within a department — delivered exactly as documented.

**Priority:** Critical

### TC-COR-3-03-025 — Assign employees to teams

**Type:** Positive

**Covers:** 3.3.3 → Assign employees to teams; Rule: A team belongs to exactly one department.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Assign employees to teams.

2. Observe the result and verify the full behavior: Assign employees to teams.

**Expected Result:** Assign employees to teams — delivered exactly as documented.

**Priority:** Critical

### TC-COR-3-03-026 — Team-level assignment targeting

**Type:** Positive

**Covers:** 3.3.3 → Team-level assignment targeting; Rule: A team belongs to exactly one department.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Team-level assignment targeting.

2. Observe the result and verify the full behavior: Team-level assignment targeting.

**Expected Result:** Team-level assignment targeting — delivered exactly as documented.

**Priority:** Critical

### TC-COR-3-03-027 — Team roster view

**Type:** Positive

**Covers:** 3.3.3 → Team roster view; Rule: A team belongs to exactly one department.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Team roster view.

2. Observe the result and verify the full behavior: Team roster view.

**Expected Result:** Team roster view — delivered exactly as documented.

**Priority:** Critical

### TC-COR-3-03-028 — Available on web and mobile

**Type:** Positive

**Covers:** 3.3.3 → Available on web and mobile; Rule: A team belongs to exactly one department.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Available on web and mobile.

2. Observe the result and verify the full behavior: Available on web and mobile.

**Expected Result:** Available on web and mobile — delivered exactly as documented.

**Priority:** Critical

### TC-COR-3-03-029 — Event logging (viewed)

**Type:** Positive

**Covers:** 3.3.3 → Event logging (viewed); Rule: A team belongs to exactly one department.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Event logging (viewed).

2. Observe the result and verify the full behavior: Event logging (viewed).

**Expected Result:** Event logging (viewed) — delivered exactly as documented.

**Priority:** Medium

### TC-COR-3-03-030 — Audit logging of the nested teams

**Type:** Positive

**Covers:** 3.3.3 → Audit logging of the nested teams; Rule: A team belongs to exactly one department.

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Audit logging of the nested teams.

2. Observe the result and verify the full behavior: Audit logging of the nested teams.

**Expected Result:** Audit logging of the nested teams — delivered exactly as documented.

**Priority:** Medium

### TC-COR-3-03-031 — Rule: A team belongs to exactly one department.

**Type:** Positive

**Covers:** 3.3.3 → A team belongs to exactly one department.; Rule: A team belongs to exactly one department..

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: A team belongs to exactly one department..

2. Observe the result and verify the full behavior: A team belongs to exactly one department..

**Expected Result:** A team belongs to exactly one department. — delivered exactly as documented.

**Priority:** High

### TC-COR-3-03-032 — Rule: An employee can belong to multiple teams but one primary department.

**Type:** Positive

**Covers:** 3.3.3 → An employee can belong to multiple teams but one primary department.; Rule: An employee can belong to multiple teams but one primary department..

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: An employee can belong to multiple teams but one primary department..

2. Observe the result and verify the full behavior: An employee can belong to multiple teams but one primary department..

**Expected Result:** An employee can belong to multiple teams but one primary department. — delivered exactly as documented.

**Priority:** High

### TC-COR-3-03-033 — Rule: Events (viewed) are logged with the account and the timestamp.

**Type:** Positive

**Covers:** 3.3.3 → Events (viewed) are logged with the account and the timestamp.; Rule: Events (viewed) are logged with the account and the timestamp..

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: Events (viewed) are logged with the account and the timestamp..

2. Observe the result and verify the full behavior: Events (viewed) are logged with the account and the timestamp..

**Expected Result:** Events (viewed) are logged with the account and the timestamp. — delivered exactly as documented.

**Priority:** High

### TC-COR-3-03-034 — Rule: The nested teams are audit-logged with the account and the timestamp.

**Type:** Positive

**Covers:** 3.3.3 → The nested teams are audit-logged with the account and the timestamp.; Rule: The nested teams are audit-logged with the account and the timestamp..

**Preconditions:** A Corporate account is active and the Corporate user is in the state required for this behavior.

**Steps:**

1. As a Corporate user, set up the precondition and perform: The nested teams are audit-logged with the account and the timestamp..

2. Observe the result and verify the full behavior: The nested teams are audit-logged with the account and the timestamp..

**Expected Result:** The nested teams are audit-logged with the account and the timestamp. — delivered exactly as documented.

**Priority:** High