Test a GTT trigger and the rule that validates it

The checks that matter

The rule under test is directional: a buy trigger has to sit below the current price, because a buy trigger above it would fire immediately and defeat the purpose.

Testing the refusal first is what proves the validation exists. A GTT created successfully tells you nothing about whether a nonsensical one would also have been created.

The flow as a test file

The last traded price is asserted first, so both the invalid and valid triggers are demonstrably on the sides of it that the test intends.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/zerodha-clone-app/gtt?reset=true
max_steps: 45
tags: [zerodha, fintech, orders]
---

# Zerodhaa Kyte 17.2: GTT trigger

Catalog objective: create a GTT with a trigger and a limit price.
Key assertion: the GTT is listed as active with the correct values.

## Verify the last traded price
With "RELIANCE" selected and "BUY" chosen, verify "Last traded price" reads "₹1,530.40".

## Verify a trigger on the wrong side is refused
Type "1600" into "Trigger price", "1605" into "Limit price", "5" into "Quantity", click "Create GTT", and verify an error says that for a buy GTT the trigger must be below the LTP of ₹1,530.40.

## Create a valid GTT
Replace "Trigger price" with "1450" and "Limit price" with "1455", then click "Create GTT".

## Verify the GTT is active with the right values
Verify a green banner titled "GTT created" names "GTT-1" as BUY 5 RELIANCE when the price hits "₹1,450.00" with a limit of "₹1,455.00", and the active GTT list shows that row with an "Active" badge.

The final assertion names the direction, the quantity, the instrument, the trigger and the limit, because a GTT that stores any one of those incorrectly executes a trade nobody asked for.

Step by step coverage

A baseline, a refusal, a creation and a record.

Both the confirmation banner and the active list are asserted. A GTT confirmed but absent from the list is an order the client believes exists and cannot manage.

Adding it to a suite

kane-cli testmd run tests/zerodha/gtt-trigger_test.md

Add the sell side, where the rule inverts and the trigger has to sit above the last traded price.

Conditional orders persist far longer than the release that created them. Evidence based QA covers retaining proof, and generating the inverse case covers producing the sell variant from the same description.