Guide · TradingView
What we need from TradingView
The exported list of trades from the strategy tester is enough for us to work with. It is a CSV and we recognise it automatically.
Deliberately incomplete guide. The step-by-step with screenshots is still pending. We don’t invent menu paths that might not match your version: write to us and we’ll walk you through it live.
How to tell whether you have the right file
Open it in any spreadsheet. If it has columns like these, it is the right one:
| Column | What it holds |
|---|---|
Trade # | The trade number, which repeats on the entry and on the exit |
Type | Whether that row is the opening or the close, and whether it was a buy or a sell |
Date/Time | When it happened |
Profit/Loss | The result |
Each trade takes up two rows, one for the entry and one for the exit, joined by the same number. We pair them up ourselves. If any were still open at the end of the period, we discard them and tell you how many there were.
How far this takes you
With the trade list we cover level 1: risk of ruin, real drawdown, behaviour in the worst scenarios, concentration of the result, and the position-management pattern.
What we will not be able to measure is overfitting, because that needs the result of every combination you tried, not just the winning one. If you tuned your strategy by hand, moving values until it looked right, tell us: that counts as searching too, and we take it into account when interpreting the rest.
Being honest about how many times you tried does not penalise you as much as you think, and hiding it makes the report say something that isn’t true.