# 1. Auto-Responder Sequences — Test Cases

User Type: **Affiliate**
Source: *Mi Digital Academy - Education CRM Features Document*
Spec: auto_responder_sequences.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 |
|---------|--------------------|----------|
| 1.1 | Create a follow-up sequence | TC-AF-7-01-001 |
| 1.1 | Configure the messages | TC-AF-7-01-002 |
| 1.1 | Set the send intervals | TC-AF-7-01-003 |
| 1.1 | Sequence triggered on new lead | TC-AF-7-01-004 |
| 1.1 | Messages sent automatically | TC-AF-7-01-005 |
| 1.1 | Sequence available on web and mobile | TC-AF-7-01-006 |
| 1.1 | Sequence event logging (created, sent) | TC-AF-7-01-007 |
| 1.1 | Audit logging of the follow-up sequence | TC-AF-7-01-008 |
| 1.1 | Rule: The sequence is triggered on a new lead. | TC-AF-7-01-001 |
| 1.1 | Rule: The messages are sent automatically at the set intervals. | TC-AF-7-01-002 |
| 1.1 | Rule: Sequence events (created, sent) are logged with the account and the timestamp. | TC-AF-7-01-003 |
| 1.1 | Rule: The follow-up sequence is audit-logged with the account and the timestamp. | TC-AF-7-01-004 |
| 1.2 | Create a nurture sequence | TC-AF-7-01-009 |
| 1.2 | Configure the value-driven content | TC-AF-7-01-010 |
| 1.2 | Set the cadence | TC-AF-7-01-011 |
| 1.2 | Sequence runs over time | TC-AF-7-01-012 |
| 1.2 | Content delivered automatically | TC-AF-7-01-013 |
| 1.2 | Sequence available on web and mobile | TC-AF-7-01-014 |
| 1.2 | Sequence event logging (created, delivered) | TC-AF-7-01-015 |
| 1.2 | Audit logging of the nurture sequence | TC-AF-7-01-016 |
| 1.2 | Rule: The sequence is value-driven. | TC-AF-7-01-009 |
| 1.2 | Rule: The content is delivered automatically over time. | TC-AF-7-01-010 |
| 1.2 | Rule: Sequence events (created, delivered) are logged with the account and the timestamp. | TC-AF-7-01-011 |
| 1.2 | Rule: The nurture sequence is audit-logged with the account and the timestamp. | TC-AF-7-01-012 |
| 1.3 | Create a win-back sequence | TC-AF-7-01-017 |
| 1.3 | Configure the re-engagement messages | TC-AF-7-01-018 |
| 1.3 | Set the inactivity trigger | TC-AF-7-01-019 |
| 1.3 | Sequence targets inactive leads | TC-AF-7-01-020 |
| 1.3 | Messages sent automatically | TC-AF-7-01-021 |
| 1.3 | Sequence available on web and mobile | TC-AF-7-01-022 |
| 1.3 | Sequence event logging (created, sent) | TC-AF-7-01-023 |
| 1.3 | Audit logging of the win-back sequence | TC-AF-7-01-024 |
| 1.3 | Rule: The sequence targets inactive leads. | TC-AF-7-01-017 |
| 1.3 | Rule: The inactivity trigger starts the sequence. | TC-AF-7-01-018 |
| 1.3 | Rule: Sequence events (created, sent) are logged with the account and the timestamp. | TC-AF-7-01-019 |
| 1.3 | Rule: The win-back sequence is audit-logged with the account and the timestamp. | TC-AF-7-01-020 |

## 1.1 Follow-Up Sequence

### TC-AF-7-01-001 — Create a follow-up sequence
**Type:** Positive
**Covers:** 1.1 → Create a follow-up sequence; Rule: The sequence is triggered on a new lead.
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Create a follow-up sequence.
2. Observe the result and verify the full behavior: Create a follow-up sequence.
**Expected Result:** Create a follow-up sequence — delivered exactly as documented.
**Priority:** Critical

### TC-AF-7-01-002 — Configure the messages
**Type:** Positive
**Covers:** 1.1 → Configure the messages; Rule: The messages are sent automatically at the set intervals.
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Configure the messages.
2. Observe the result and verify the full behavior: Configure the messages.
**Expected Result:** Configure the messages — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-003 — Set the send intervals
**Type:** Positive
**Covers:** 1.1 → Set the send intervals; Rule: Sequence events (created, sent) are logged with the account and the timestamp.
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Set the send intervals.
2. Observe the result and verify the full behavior: Set the send intervals.
**Expected Result:** Set the send intervals — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-004 — Sequence triggered on new lead
**Type:** Positive
**Covers:** 1.1 → Sequence triggered on new lead; Rule: The follow-up sequence is audit-logged with the account and the timestamp.
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Sequence triggered on new lead.
2. Observe the result and verify the full behavior: Sequence triggered on new lead.
**Expected Result:** Sequence triggered on new lead — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-005 — Messages sent automatically
**Type:** Positive
**Covers:** 1.1 → Messages sent automatically
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Messages sent automatically.
2. Observe the result and verify the full behavior: Messages sent automatically.
**Expected Result:** Messages sent automatically — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-006 — Sequence available on web and mobile
**Type:** Positive
**Covers:** 1.1 → Sequence available on web and mobile
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Sequence available on web and mobile.
2. Observe the result and verify the full behavior: Sequence available on web and mobile.
**Expected Result:** Sequence available on web and mobile — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-007 — Sequence event logging (created, sent)
**Type:** Positive
**Covers:** 1.1 → Sequence event logging (created, sent)
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Sequence event logging (created, sent).
2. Observe the result and verify the full behavior: Sequence event logging (created, sent).
**Expected Result:** Sequence event logging (created, sent) — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-008 — Audit logging of the follow-up sequence
**Type:** Positive
**Covers:** 1.1 → Audit logging of the follow-up sequence
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, perform the follow-up sequence action.
2. Open the audit log and verify the entry for the action.
**Expected Result:** The follow-up sequence action is recorded in the audit log with the account and the timestamp.
**Priority:** Critical


## 1.2 Nurture Sequence

### TC-AF-7-01-009 — Create a nurture sequence
**Type:** Positive
**Covers:** 1.2 → Create a nurture sequence; Rule: The sequence is value-driven.
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Create a nurture sequence.
2. Observe the result and verify the full behavior: Create a nurture sequence.
**Expected Result:** Create a nurture sequence — delivered exactly as documented.
**Priority:** Critical

### TC-AF-7-01-010 — Configure the value-driven content
**Type:** Positive
**Covers:** 1.2 → Configure the value-driven content; Rule: The content is delivered automatically over time.
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Configure the value-driven content.
2. Observe the result and verify the full behavior: Configure the value-driven content.
**Expected Result:** Configure the value-driven content — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-011 — Set the cadence
**Type:** Positive
**Covers:** 1.2 → Set the cadence; Rule: Sequence events (created, delivered) are logged with the account and the timestamp.
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Set the cadence.
2. Observe the result and verify the full behavior: Set the cadence.
**Expected Result:** Set the cadence — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-012 — Sequence runs over time
**Type:** Positive
**Covers:** 1.2 → Sequence runs over time; Rule: The nurture sequence is audit-logged with the account and the timestamp.
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Sequence runs over time.
2. Observe the result and verify the full behavior: Sequence runs over time.
**Expected Result:** Sequence runs over time — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-013 — Content delivered automatically
**Type:** Positive
**Covers:** 1.2 → Content delivered automatically
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Content delivered automatically.
2. Observe the result and verify the full behavior: Content delivered automatically.
**Expected Result:** Content delivered automatically — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-014 — Sequence available on web and mobile
**Type:** Positive
**Covers:** 1.2 → Sequence available on web and mobile
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Sequence available on web and mobile.
2. Observe the result and verify the full behavior: Sequence available on web and mobile.
**Expected Result:** Sequence available on web and mobile — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-015 — Sequence event logging (created, delivered)
**Type:** Positive
**Covers:** 1.2 → Sequence event logging (created, delivered)
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Sequence event logging (created, delivered).
2. Observe the result and verify the full behavior: Sequence event logging (created, delivered).
**Expected Result:** Sequence event logging (created, delivered) — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-016 — Audit logging of the nurture sequence
**Type:** Positive
**Covers:** 1.2 → Audit logging of the nurture sequence
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, perform the nurture sequence action.
2. Open the audit log and verify the entry for the action.
**Expected Result:** The nurture sequence action is recorded in the audit log with the account and the timestamp.
**Priority:** Critical


## 1.3 Win-Back Sequence

### TC-AF-7-01-017 — Create a win-back sequence
**Type:** Positive
**Covers:** 1.3 → Create a win-back sequence; Rule: The sequence targets inactive leads.
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Create a win-back sequence.
2. Observe the result and verify the full behavior: Create a win-back sequence.
**Expected Result:** Create a win-back sequence — delivered exactly as documented.
**Priority:** Critical

### TC-AF-7-01-018 — Configure the re-engagement messages
**Type:** Positive
**Covers:** 1.3 → Configure the re-engagement messages; Rule: The inactivity trigger starts the sequence.
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Configure the re-engagement messages.
2. Observe the result and verify the full behavior: Configure the re-engagement messages.
**Expected Result:** Configure the re-engagement messages — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-019 — Set the inactivity trigger
**Type:** Positive
**Covers:** 1.3 → Set the inactivity trigger; Rule: Sequence events (created, sent) are logged with the account and the timestamp.
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Set the inactivity trigger.
2. Observe the result and verify the full behavior: Set the inactivity trigger.
**Expected Result:** Set the inactivity trigger — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-020 — Sequence targets inactive leads
**Type:** Positive
**Covers:** 1.3 → Sequence targets inactive leads; Rule: The win-back sequence is audit-logged with the account and the timestamp.
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Sequence targets inactive leads.
2. Observe the result and verify the full behavior: Sequence targets inactive leads.
**Expected Result:** Sequence targets inactive leads — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-021 — Messages sent automatically
**Type:** Positive
**Covers:** 1.3 → Messages sent automatically
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Messages sent automatically.
2. Observe the result and verify the full behavior: Messages sent automatically.
**Expected Result:** Messages sent automatically — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-022 — Sequence available on web and mobile
**Type:** Positive
**Covers:** 1.3 → Sequence available on web and mobile
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Sequence available on web and mobile.
2. Observe the result and verify the full behavior: Sequence available on web and mobile.
**Expected Result:** Sequence available on web and mobile — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-023 — Sequence event logging (created, sent)
**Type:** Positive
**Covers:** 1.3 → Sequence event logging (created, sent)
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, set up the precondition and perform: Sequence event logging (created, sent).
2. Observe the result and verify the full behavior: Sequence event logging (created, sent).
**Expected Result:** Sequence event logging (created, sent) — delivered exactly as documented.
**Priority:** High

### TC-AF-7-01-024 — Audit logging of the win-back sequence
**Type:** Positive
**Covers:** 1.3 → Audit logging of the win-back sequence
**Preconditions:** A Affiliate account is active and the Affiliate is in the state required for this behavior.
**Steps:**
1. As a Affiliate, perform the win-back sequence action.
2. Open the audit log and verify the entry for the action.
**Expected Result:** The win-back sequence action is recorded in the audit log with the account and the timestamp.
**Priority:** Critical