Test enrolling a contact in an email sequence

The checks that matter

The enrolment has to be visible in two independent places, because a sequence running without a timeline entry is impossible to audit.

The step position is asserted in both places. An enrolment that starts at the wrong step skips emails the prospect was meant to receive, and the count of active enrolments is what proves exactly one was created.

The flow as a test file

The sequence is selected by its full label including its shape, four steps over twelve days, so a sequence renamed or reconfigured is visible in the test.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/hubspot-clone-app/sequences?reset=true
max_steps: 40
tags: [hubspot, crm, marketing]
---

# Hubsprout 29.3: Email sequence enrollment

Catalog objective: enrol a contact in a sequence.
Key assertion: the sequence is active on the contact timeline.

## Choose the contact and the sequence
Select "Mira Shah - mira@northgate.test" in "Contact", select "New lead nurture - 4 steps over 12 days" in "Sequence".

## Enrol
Click "Enrol" and verify a green banner reads "Mira enrolled in "New lead nurture". It is now on their timeline."

## Verify the enrolment is active
Verify the Enrolments card shows "Active enrolments" of 1 with a "Mira Shah" row reading "New lead nurture · step 1 of 4" and an "Active" badge.

## Verify it is on the contact timeline
Verify the "Mira's timeline" card contains the entry "Enrolled in sequence "New lead nurture" - step 1 of 4".

The timeline entry is asserted by its exact text, because the timeline is what a rep reads before calling and a missing entry leads to a duplicate outreach.

Step by step coverage

A selection, an enrolment, the active record and the timeline.

An automation that sends email without appearing on the record is the kind of thing that surfaces as a complaint rather than a bug report.

Adding it to a suite

kane-cli testmd run tests/hubspot/sequence-enrollment_test.md

Add an unenrolment, since stopping a sequence matters more than starting one when someone asks not to be contacted.

Outbound automation has consequences outside your product. Running Kane CLI in CI covers regular checks, and Kane CLI as a QA agent covers the surrounding suite.