Test an options chain and the premium for a strike

The flow under test

The assertions that matter are the ones a trader would notice being wrong only after committing money.

• The underlying price - $226.80, which every moneyness label is relative to.
• The strike list - 215 through 235, present and in order.
• The moneyness labels - 215 marked in the money and 230 out of the money, which is the classification the price implies.
• The premium - a bid and ask of $3.25 and $3.35, and a cost of $335.00 for one contract.

The final figure is the one worth asserting hardest. A contract priced at $3.35 costs $335.00 because it covers a hundred shares, and a chain that displays the per-share premium as the contract cost understates the trade by two orders of magnitude.

The test file

The moneyness labels are asserted against specific strikes rather than checked as a set, because the boundary between them moves with the underlying price and is where the classification breaks.

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

# Robinhud 16.5: Options chain

Catalog objective: open an options chain and select an expiry and a strike.
Key assertion: the premium renders for the selection.

## Choose the underlying and expiry
Select "AAPL" in "Underlying" and "2026-09-26" in "Expiry", then verify "AAPL last" reads "$226.80".

## Verify the chain
Verify the calls table for 2026-09-26 lists strikes 215, 220, 225, 230 and 235, with 215 marked "ITM" and 230 marked "OTM".

## Select a strike
Click "Select" on the 230 strike and verify a "Selected contract" card appears.

## Verify the premium for the selection
Verify the contract reads "AAPL 2026-09-26 $230.00 Call" with "Bid / Ask" of "$3.25 / $3.35" and "Cost for 1 contract (100 shares)" of "$335.00".

The selected contract is asserted by its full description, underlying, expiry, strike and type, so a selection that lands on a neighbouring row fails before the premium is read.

Step by step coverage

Two steps on the chain, two on the contract.

Expiry is part of the contract description assertion. An options interface that keeps the strike and loses the expiry produces a valid looking trade on the wrong date.

Running it

kane-cli testmd run tests/robinhood/options-chain_test.md

Add a puts variant, since the moneyness logic inverts and that inversion is a classic off-by-one.

Dense tables are where plain English assertions save the most selector maintenance. How assertions resolve on a live page covers the mechanism, and checking the UI before a pull request is where a chain change should be caught.