Test lead creation and the owner it lands on

The flow under test

The ownership assertion is the only one of these that decides whether a human ever actually sees the lead.

• Required fields are enforced - an empty save produces inline errors on last name and company.
• The lead is created - with an id of 00Q101 and the details entered.
• The owner is assigned - Marco Oduya, asserted on the confirmation and again in the list.
• The list count moves - the all open leads view reporting two rows.

Asserting the owner in the list view rather than only on the confirmation is what catches an assignment that is accepted on the form and dropped on save. That is a common CRM defect and it is invisible from the record page.

The test file

The empty save comes first, which is both the cheapest place to test validation and what a distracted rep actually does.

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

# Salesfource 28.1: Lead creation

Catalog objective: create a lead through the form with its required fields.
Key assertion: the lead appears in the list view with the correct owner.

## Open the new lead form
Click "New Lead" and verify a "New Lead" form appears with "Last Name *" and "Company *" marked as required.

## Verify the required fields are enforced
Click "Save" with the form empty and verify inline errors appear on "Last Name *" and "Company *".

## Fill in the lead
Type "Rivera" into "Last Name *", "Riverfield FC" into "Company *", "sam@riverfield.test" into "Email", select "Partner Referral" in "Lead Source", and select "Marco Oduya" in "Lead Owner".

## Verify the lead is in the list with the right owner
Click "Save" and verify a green banner titled "Lead created" names lead "00Q101" for Rivera at Riverfield FC owned by Marco Oduya, and the "All Open Leads (2)" table shows that row with an owner of "Marco Oduya".

The required markers are asserted as part of the form, so a field that stops being required is visible in the test rather than only surfacing as dirty data months later.

Step by step coverage

A form, a refusal, the data and the record.

Lead source is captured too. It is the field that decides attribution reporting, and it is the one most often left to a default nobody chose.

Running it

kane-cli testmd run tests/salesforce/lead-creation_test.md

Point this at a sandbox org. The flow creates a real record in whichever environment the front matter names.

CRM customisation changes faster than the code around it, which makes a plain English test more durable than a selector-based one. How browser agents read a page covers why, and the test.md format covers the file layout.