Test a deal moving stage without losing its value

Failure modes in this flow

One move changes four displayed numbers, and only one of them is the card itself.

• The card amount - $24,000.00, unchanged by a stage move.
• The source column - falling to $0.00 once the only deal leaves it.
• The destination column - now carrying the deal and its value.
• The pipeline total - still $31,500.00, because moving a deal does not change how much is in the pipeline.

The pipeline total is the strongest assertion in the file. It is the number reported upward, and a move that double-counts or drops a deal changes it while every individual card still looks correct.

Writing the objective

The confirmation banner states the amount is unchanged, and the test asserts that wording as well as the figures, so the interface and the data are checked against each other.

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

# Hubsprout 29.2: Deal pipeline drag

Catalog objective: move a deal across pipeline stages.
Key assertion: the deal stage changes and the amount is preserved.

## Verify where the deal starts
Verify the "Northgate Supply - annual" card sits in the "Qualified to buy" column showing "$24,000.00", and the page subtitle reads "2 deals · $31,500.00".

## Move the deal
On the "Northgate Supply - annual" card, select "Presentation scheduled" in its "Stage for Northgate Supply - annual" dropdown, and verify a green banner reads "Northgate Supply - annual moved to Presentation scheduled. Amount still $24,000.00."

## Verify the stage changed
Verify the "Presentation scheduled - $24,000.00" column now holds the "Northgate Supply - annual" card and the "Qualified to buy - $0.00" column is empty.

## Verify the amount was preserved
Verify the deal record still shows "$24,000.00", the total pipeline still reads "$31,500.00", and the deal history contains "Stage Qualified to buy -> Presentation scheduled, amount unchanged at $24,000.00".

The deal history is asserted at the end, since a stage change without an audit entry cannot answer who moved a deal or when.

The assertions in detail

A starting position, a move, the board, and the record.

Asserting the source column fell to zero is what proves the deal moved rather than being copied, which is a real failure mode on a board that rerenders.

Running it locally

kane-cli testmd run tests/hubspot/deal-pipeline-drag_test.md

Add a move on a column holding several deals, since totals that are correct with one deal often break with two.

Forecast surfaces deserve checking on every release. Checking the UI before a pull request covers that, and evidence based QA covers keeping the proof.