1. Capital Market Domain Overview & Business Flow
The capital market domain deals with buying and selling long-term financial instruments such as equities, bonds, derivatives, commodities, mutual funds, and ETFs. Software testing in this domain ensures accuracy, compliance, risk control, settlement integrity, and high availability.
High-Level Business Flow (Trade Lifecycle)
- Order Placement – Client places order via OMS/UI/API
- Order Validation – Price, quantity, margin, limits
- Execution – Order matched at exchange
- Trade Capture – Trade booked in systems
- Clearing – Netting & obligation calculation
- Settlement – Funds & securities exchange (T+1 / T+2)
- Reporting – Contract notes, regulatory reports
2. Capital Market Domain Modules (Testing Perspective)
| Module | Description |
| Front Office | Trading screens, order entry, pricing |
| Order Management System (OMS) | Order routing, modification, cancellation |
| Execution Management System (EMS) | Exchange connectivity |
| Risk & Margin | Exposure, VAR, SPAN, limits |
| Clearing & Settlement | Trade netting, settlement cycles |
| Back Office | Accounting, reconciliation |
| Corporate Actions | Dividends, splits, mergers |
| Market Data | Real-time prices, OHLC |
| Regulatory & Compliance | SEBI, FINRA, MiFID reports |
3. Capital Market Domain Testing Interview Questions & Answers
Basic Level (Freshers)
1. What is capital market domain testing?
Testing financial systems involved in trading, clearing, settlement, and reporting of securities.
2. What are primary instruments traded?
Equities, bonds, derivatives, mutual funds, ETFs, commodities.
3. What is an order?
A client instruction to buy/sell a security with price, quantity, and type.
4. Difference between market and limit order?
Market executes at best price; limit executes at specified price.
5. What is T+2 settlement?
Settlement happens two business days after trade date.
Intermediate Level (2–4 Years)
6. Explain trade lifecycle.
Order → Execution → Trade capture → Clearing → Settlement → Reporting.
7. What is OMS testing?
Validating order placement, modification, cancellation, routing.
8. What is margin testing?
Ensuring sufficient margin before trade execution.
9. What is corporate action?
Company events impacting securities like dividends, splits.
10. What is straight-through processing (STP)?
Automated flow without manual intervention.
Advanced Level (5+ Years)
11. How do you test exchange connectivity?
Using mock FIX messages, latency checks, failover scenarios.
12. Explain netting in clearing.
Combining multiple trades to reduce settlement obligations.
13. What are regulatory validations?
Trade reporting accuracy, audit trails, timestamp integrity.
14. How do you test high-frequency trading systems?
Performance, latency, concurrency, memory usage.
15. Explain front-office vs back-office testing.
Front office focuses on trading; back office on settlement and accounting.
4. Scenario-Based Domain Testing Questions
SIT / UAT Scenarios
16. Client places buy order without sufficient margin – expected behavior?
Order rejected with proper error message.
17. Exchange down during execution – how system handles?
Order queued or failed with retry mechanism.
18. Partial fill scenario testing?
Validate remaining quantity stays open.
19. Trade amended post-execution – what to test?
Audit trail, regulatory updates, downstream impact.
20. Settlement holiday impact?
Settlement date shifts correctly.
5. Real-Time Testing Workflows
Equity Trade Example
Client → Trading UI → OMS → Exchange → Clearing Corp → Depository → Bank
Sample Business Rules
- Price bands validation
- Quantity freeze limits
- Margin percentage based on instrument
- Settlement cycle by market
6. Sample Test Case – Capital Market
| Test Case ID | CM_EQ_001 |
| Scenario | Buy equity with insufficient margin |
| Pre-condition | Account balance < required margin |
| Steps | Place buy order |
| Expected Result | Order rejected |
| Status | Pass |
7. Database, API & UI Validation
Database Validation
SELECT trade_id, status
FROM trades
WHERE trade_date = CURRENT_DATE;
API Validation
- Validate FIX / REST responses
- Status codes (200, 400, 500)
- Trade IDs consistency
UI Validation
- Price accuracy
- Real-time updates
- Order book reflection
8. Production Defect Examples
| Defect | Root Cause |
| Wrong settlement date | Holiday calendar mismatch |
| Duplicate trades | Retry logic failure |
| Margin miscalculation | Incorrect risk rules |
| Price mismatch | Market data latency |
9. Risk Areas & Test Design Approach
High-Risk Areas
- Settlement processing
- Regulatory reporting
- Corporate actions
- Real-time pricing
Test Approach
- Requirement analysis (BRD/FRD)
- Risk-based testing
- End-to-end validation
- Automation + performance testing
10. BRD / FRD Validation Checklist
| Document | What to Validate |
| BRD | Business rules, flows |
| FRD | Field mapping, APIs |
| UI Specs | Screen behavior |
| Data Model | Tables & relations |
11. Quick Revision Cheat Sheet
- OMS = Order flow control
- EMS = Execution connectivity
- STP = Automation end-to-end
- VAR = Risk measurement
- T+2 = Settlement cycle
12. FAQs – Capital Market Domain Testing
Q1. Is capital market testing tough?
Moderate to complex; domain knowledge is key.
Q2. Do testers need finance background?
Helpful but not mandatory.
Q3. Which tools are used?
SQL, Postman, FIX simulators, JIRA.
Q4. Automation scope?
Regression, order flow, pricing validations.