Backtest: Know What History Can Answer
A beginner-safe Backtest lesson for turning a trade idea into admissible evidence: hypothesis first, rulebook second, data window third, and result last.
Lesson promise
Frame the question
What question am I really asking history to answer?
Check the evidence
Use 5 guided chapters to read freshness, confidence, and caveats in order.
Move into the tool
Open Open Strategy Backtester with a checklist instead of a blank screen.
Educational workflow only. No trade recommendations, personalized advice, leverage guidance, or guaranteed outcomes.
Chapter 01
Ask a question history can answer
Trader question
What question am I really asking history to answer?
A backtest can inspect how a defined rulebook behaved in a defined historical window. It cannot say what the next live trade will do, so the first skill is to write the question before looking at the chart.
Desk checklist
- Name the market idea in plain language.
- Keep the chart hidden until the assumptions are visible.
- Write one thing the backtest cannot answer.
Interactive proof
Backtest workspace and result empty state
Use the courtroom lab to admit hypothesis, rulebook, data window, and result in the right order.
The Backtest lesson keeps the result last. Until the hypothesis, rulebook, and data window are visible, total return and win rate are not interpretable.
Interactive desk lab
Backtest Courtroom Lab
A practical first Backtest lab for admitting hypothesis, rulebook, data window, and result in the right order before reading a performance chart.
A practical first Backtest lab for admitting hypothesis, rulebook, data window, and result in the right order before reading a performance chart.
Evidence before the chart
A trade idea enters the courtroom, then hypothesis, rulebook, data window, and result appear in the only order that makes the chart meaningful.
A vague trade idea lands on the desk.
Hypothesis, rulebook, and data window stamp in before the chart.
The result card appears only after assumptions are visible.
The final frame labels the result as evidence, not a forecast.
Lesson notes
The full chapter walkthrough in reading form — use it to review the lesson or skim ahead before working through the interactive steps above.
Chapter 01
Ask a question history can answer
What question am I really asking history to answer?
A backtest can inspect how a defined rulebook behaved in a defined historical window. It cannot say what the next live trade will do, so the first skill is to write the question before looking at the chart.
Backtest workspace and result empty state
- Name the market idea in plain language.
- Keep the chart hidden until the assumptions are visible.
- Write one thing the backtest cannot answer.
Chapter 02
Separate the idea from the rulebook
What exact rule did I test, not just what did I believe?
Ideas like buy dips, follow momentum, or trade the festival window are not testable until they become entry, exit, risk, and market assumptions. If the rule changes, the test changes.
Strategy Builder entry, exit, stop, and target blocks
- Turn narrative into entry logic.
- Define exit logic before reading the result.
- Keep stop loss and take profit visible as assumptions.
Chapter 03
Lock the sample before the result
Which market, candle, date range, and capital assumption framed the evidence?
The same rule can look different on 1M, 1Y, 3Y, MAX, or another metal. The result is only interpretable when the learner knows the data window and current tool boundary.
Metal, venue, candle, range, and initial capital controls
- Confirm the current visual flow is COMEX/USD daily data.
- Choose the date range before reading return.
- Treat initial capital as a simulation input.
Chapter 04
Read the first run as evidence
What did the test show, and what did it not show?
A profitable first run is not a verdict. It is an evidence card that still needs risk inspection, drawdown reading, trade-count checks, cost awareness, and reruns.
Results metrics, equity curve, and Strategy read card
- Read drawdown before total return.
- Check trade count before trusting win rate.
- Treat the grade as evidence quality, not approval.
Chapter 05
Name what could weaken the read
What would make this backtest less trustworthy?
A serious backtest ends with a caveat: the rule may fail on another window, another metal, another cost model, or live execution. Naming that caveat keeps confidence useful instead of dangerous.
Save strategy description and next validation note
- Name one changed rule that would create a new test.
- Name one market regime the sample may have missed.
- Save the caveat beside the result.
Sources used for this tutorial
Next step
Open the tool with the checklist beside you.
Move from the lesson into the matching Bullion Brains tool, keep the checklist visible, and treat the output as evidence until the caveats are clear.