Test a landing page form creating a CRM contact

The flow under test

The test spans two systems, and the assertion that matters is on the far side of the handoff.

• The form accepts the data - five fields including phone and company.
• The visitor is thanked - a confirmation card, which is all most tests check.
• The contact is created - with the submitted values echoed back.
• The CRM has it - a contact count of two and a row carrying every field including the original source.

Original source is the field worth asserting hardest. It is set automatically rather than typed, it decides attribution, and a form that creates contacts with a blank source makes every channel report wrong without losing a single lead.

The test file

The phone is asserted only in the CRM, not on the confirmation, which is deliberate: it is the field most likely to be captured for display and dropped on write.

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

# Hubsprout 29.1: Form to contact creation

Catalog objective: submit a landing page form and verify a contact is created.
Key assertion: the contact exists with the submitted field values.

## Fill in the landing page form
Type "Sam" into "First name", "Rivera" into "Last name", "sam@riverfield.test" into "Work email", "Riverfield FC" into "Company" and "555 0110" into "Phone".

## Submit it
Click "Download the report" and verify a green card titled "Thanks - your download is on its way" appears.

## Verify the contact was created with the form values
Verify the confirmation shows "Contact created" of "Sam Rivera", "Email" of "sam@riverfield.test", "Company" of "Riverfield FC" and "Original source" of "Landing page form".

## Verify the record in the CRM
Click "See the contact in the CRM" and verify "Contact count" reads 2 and the table has a "Sam Rivera" row with email "sam@riverfield.test", company "Riverfield FC", phone "555 0110" and source "Landing page form".

The contact count is asserted alongside the row, proving one contact was created rather than a duplicate pair from a double submit.

Step by step coverage

A form, a confirmation, and the record on the other side.

Checking the CRM rather than the thank-you card is the entire value here. The confirmation is produced by the page that collected the data, not by the system that stored it.

Running it

kane-cli testmd run tests/hubspot/form-to-contact_test.md

Add a duplicate submission with the same email, since merging onto an existing contact rather than creating a second is usually the intended behaviour.

Attribution fields are set by code rather than by a person and are rarely checked. Running Kane CLI in CI covers catching a regression, and the test.md format covers the file layout.