Nasdaq Short-Only EA Tests: How to Read the Evidence
MARKET CRASHES & BEAR MARKETS
A practical evidence checklist for Nasdaq short-only robot reports: contract, settings, downside windows, rebounds and forward results.

← Explore the crash & bear-market research hub
By EA LAB Editorial • Published October 14, 2026 • Educational research and scenario analysis • Expanded October 14, 2026
Market Scanner: latest independent video reviews →
Code capability
Separate SELL test
Stress cases
Published evidence
A Nasdaq short-only EA needs a Nasdaq-specific SELL-only test. A report on another instrument, or a combined BUY-and-SELL report, cannot establish that claim. This article is an evaluation protocol, not a published robot performance result.
Start with the contract and version
Identify the underlying index, broker symbol, cash or futures-based contract, trading sessions, point value, account currency and costs. Record the EA version and exact settings. The word “Nasdaq” in a title is not sufficient identification.
Verify short-only behavior
Check that new BUY entries are disabled or absent by design. Inspect the report’s direction split and representative trades. Explain how the robot closes SELL positions and handles opposite signals. A screenshot of one short trade does not establish behavior for the whole test.
Use more than the best decline
Include falling markets, rebounds, sideways periods and rising markets. Publish the date windows and explain why they were selected. If historical tick data are limited, disclose the range available rather than implying coverage of every famous crash.
Read the metrics together
Net profit without equity drawdown can conceal large floating losses. A high win rate can coexist with rare severe losses. A small number of trades may be insufficient to judge stability. Inspect exposure, holding time, worst losing sequence, financing and the sensitivity to execution assumptions.
EA LAB’s publication requirements for this collection
- Documented short-only configuration or dedicated implementation.
- Named Nasdaq-linked instrument and supported specification.
- Original report for the exact version and settings.
- Separate development and evaluation periods.
- Disclosure of scaling, grid or martingale behavior.
- Limits and observed failure conditions.
The collection is prepared for products meeting these conditions. Its creation does not mean that all existing robots qualify or that any new robot has already passed the tests.
Forward evidence
A forward record should show the start date, version changes, account type and costs. Demo and live records should be labeled. Do not silently restart a losing record and present only the replacement account.
Recurring historical crashes are a reason to build an auditable process now. They are not evidence that a particular short robot will profit during the next decline.
Read a report as a chain of evidence
Begin with identity, then behavior, then performance. Identity means the code version, preset and contract match the advertised product. Behavior means the report’s trades reflect the stated direction, entry and exit rules. Performance is the result produced by that specific combination over those specific dates. Skipping the first two steps makes an attractive profit figure difficult to interpret.
A report should let a reader trace at least several entries from the stated signal to the actual transaction. Include an example winner, an example loser and a trade from a difficult rebound. Showing only the best trade explains very little about the process. If the signal uses completed candles, the example should show the confirmation candle and the subsequent executable entry separately.
For a Nasdaq-focused product, identify the underlying contract rather than assuming a broker symbol is self-explanatory. Contract value, trading hours and financing can differ between similarly named instruments. Store the specification used for the test so later changes do not silently alter the meaning of a preset.
The minimum evidence packet
| File or record | What it establishes | What it does not establish |
|---|---|---|
| Versioned EA and preset | The rules and inputs selected | Profitability on another symbol |
| Original test report | Observed simulated trades and account result | A future live result |
| Equity curve and trade list | Floating-risk path and transaction sequence | Guaranteed fills in a future disruption |
| Evaluation / forward segment | Behavior after development choices | Universal robustness |
Worked example: two reports with the same net result
Imagine two test reports each ending 20% above their starting deposit. Report A reached a 7% maximum equity drawdown and completed 180 trades. Report B reached 35% drawdown and completed 12 trades. Those invented numbers do not tell us which system is better for every purpose, but they show why final profit alone cannot describe the experience of holding the strategy.
Next suppose most of B’s profit came from one trade. A missed fill, earlier stop or different evaluation period could change its result substantially. The relevant sensitivity test removes or perturbs that event and explains what happens. For A, investigate whether many similar trades are really independent or merely a series of entries during one favorable market regime.
A high trade count does not cure overfitting. A larger sample can still be dominated by one instrument, one session or one directional period. Publish the distribution of results by regime and time, and explain whether the chosen parameters were selected after inspecting those same trades.
Publication standards for crash performance claims
Use an exact claim such as “this version, on this broker symbol, over these dates, produced this simulated result.” The more general statement “it makes money in crashes” requires evidence across multiple relevant episodes and adverse control periods. Even then, future execution remains uncertain.
Show losses beside profits. If bullish periods are unfavorable, explain how the mandate handles them and whether the filter was tested without hindsight. If the product adds to losing positions, disclose that behavior before a reader sees the balance curve. A simple label such as trend-following is insufficient when exposure scaling drives the account risk.
Finally, preserve the original evidence rather than recreating a balance line from an image. A plotted performance chart should be traceable to actual report data. Until that packet exists for a new SELL-only robot, the collection can explain the methodology without implying a result has already been achieved.
Frequently asked questions
Is there a performance result in this article?
No. It describes the evidence required before publishing a product-specific study.
Can a gold report qualify a Nasdaq robot?
No. It can document a gold test; a Nasdaq claim needs its own appropriate evidence.
Continue your research
- How to Backtest an EA Across Bear and Bull Markets
- Short-Only vs Long-and-Short EAs in a Bear Market
- Martingale Short Robots During a Crash: Basket Targets, Equity Risk and Pyramiding
Explore the MT5 Robot Library • Visit Strategy Lab
Trading involves risk, including substantial losses. Historical market behavior and backtests do not guarantee future results. An EA automates its rules; it does not guarantee profit or portfolio protection.