Test creating a price alert above the current price

The flow under test

Four values have to be stored together, and the direction is the one that inverts the meaning of everything else.

• The reference price - $3,120.40, which the target is relative to.
• The direction - above rather than below, which is the whole semantics of the alert.
• The target - $3,500.00, with the interface showing the percentage distance from the current price.
• The saved rule - listed with an active status, stating both direction and target.

Asserting the direction in the saved rule, and not only at selection, is what catches an alert stored with an inverted condition. It would fire immediately, which a customer reads as a bug in the price feed rather than in the alert.

The test file

The current price is asserted before the target is set, so the alert is demonstrably above market rather than assumed to be.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/coinbase-clone-app/alerts?reset=true
max_steps: 40
tags: [coinbase, fintech, alerts]
---

# Coinbaze 18.4: Price alert

Catalog objective: set a price alert on ETH.
Key assertion: the alert is saved with its target price.

## Choose the asset
Select "ETH" in "Asset" and verify "Current price" reads "$3,120.40".

## Set the direction and target
Choose "Price goes above" and type "3500" into "Target price", then verify a badge shows the percentage difference from the current price.

## Create the alert
Click "Create alert" and verify a green banner titled "Alert created" says you will be notified when "ETH" goes "above" "$3,500.00".

## Verify the alert is saved
Verify the "Your alerts (1)" card lists "ETH above $3,500.00" with an active status badge.

The step ceiling is 40, matching a short flow with a single form and no payment.

Step by step coverage

A reference, a rule, a creation and a record.

The alert count in the card heading is asserted too, which proves one rule was created rather than a duplicate pair.

Running it

kane-cli testmd run tests/coinbase/price-alert_test.md

Add a below-market variant, since the direction inverts and that inversion is where alert logic usually breaks.

Notification rules are set once and trusted indefinitely. Generating the inverse case covers producing the pair, and Kane CLI as a QA agent covers where short checks like this sit in a suite.