Power Your Software Testing with AI Agents and Cloud
The Native AI-Agentic Cloud Platform to Supercharge Quality Engineering. Test Intelligently and Ship Faster.
- TestMu AI (Formerly LambdaTest)
- /
- Use Cases
- /
- Test an intraday order and its margin requirement
Test an intraday order and its margin requirement
Intraday product means leverage, and leverage means the margin shown has to be a fifth of the order value.
Published on:
An intraday product carries leverage, which means the margin a broker blocks is a fraction of the order value. Getting that fraction wrong either blocks a client who should be able to trade or extends credit that was never approved.
This use case places an intraday limit order on the Zerodhaa Kyte clone and checks the margin arithmetic.
Failure modes in this flow
The margin figure is the one number here that cannot be checked by eye, which is exactly why it belongs in an assertion.
- Order value - 15,000 rupees, which is ten shares at a limit of 1,500.
- Margin required - 3,000 rupees, a fifth of the value because the intraday product carries five times leverage.
- The order status - open rather than filled, because the limit sits below the last traded price.
- The order book - a row with the order number carrying an open badge.
Asserting the margin against the order value in the same step is what makes the leverage ratio verifiable. Either figure alone is just a number on a screen.
Note: Kane CLI asserts several related figures in one instruction, so a leverage ratio can be pinned without splitting it across three steps. Try it on TestMu AI. Try free!
Writing the objective
The product and the order type are both set explicitly rather than relying on defaults, because the margin calculation depends entirely on which product is selected.
---
mode: testing
url: https://my-testing-repo-main.vercel.app/zerodha-clone-app/orders?reset=true
max_steps: 45
tags: [zerodha, fintech, trading]
---
# Zerodhaa Kyte 17.1: Intraday order
Catalog objective: place an intraday limit order on a stock.
Key assertion: the order appears in the order book as open.
## Set the order up
With "RELIANCE" selected, choose "MIS - Intraday" as the product and "LIMIT" as the order type, set "Quantity" to "10" and "Price" to "1500".
## Verify the margin benefit of intraday
Verify "Order value" reads "₹15,000.00" and "Margin required" reads "₹3,000.00", which is a fifth of the value because MIS carries 5x leverage.
## Place the order
Click "Buy RELIANCE" and verify a banner titled "Order OPEN" shows a placed price of "₹1,500.00", a status of "OPEN" and an order number of "26092601".
## Verify it sits in the order book as open
Verify the order book has a row for "26092601" carrying an "OPEN" badge, since the limit of ₹1,500.00 is below the last traded price of ₹1,530.40.The fourth step states why the order is open, that the limit is below the last traded price, which keeps the expected outcome and its reason together in the file.
The assertions in detail
Setup, the calculation, the action, the record.
| Step | What it proves |
|---|---|
| Set the order up | Product, order type, quantity and price can all be set |
| Verify the margin benefit of intraday | Order value and margin are both shown and in the right ratio |
| Place the order | The order is accepted at the limit price with an order number |
| Verify it sits in the order book as open | The order is recorded as open, not filled |
Order number, status and price are all asserted on placement. A broker that returns an order number without a status leaves the client unsure whether they have a position.
Running it locally
kane-cli testmd run tests/zerodha/intraday-order_test.mdAdd a delivery product variant, since the margin requirement changes completely and that difference is the point of having two products.
Margin rules change with regulation more often than with releases. Deriving a suite from written requirements covers keeping the expected ratios tied to their source, and running in CI covers catching drift automatically.
Author
Bhawana is a Community Evangelist at TestMu AI with over 3 years of experience creating technically accurate, strategy-driven content in software testing. She has authored 50+ blogs on test automation, cross-browser testing, mobile testing, and real device testing. She also serves as Product Marketing Manager for Kane CLI, the command-line tool that runs browser automation from the terminal using natural-language flows in a real Chrome browser. Bhawana is certified in KaneAI, Selenium, Appium, Playwright, and Cypress, reflecting her hands-on knowledge of modern automation practices. On LinkedIn, she is followed by 6000+ QA engineers, testers, AI automation testers, and tech leaders.
Intraday Order FAQs
Did you find this page helpful?
TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance
- Advanced access controls
- Advanced data retention rules
- Advanced Local Testing
- Premium Support options
- Early access to beta features
- Private Slack Channel
- Unlimited Manual Accessibility DevTools Tests




