Execution Pitfalls

 
Find out why your EA's backtest doesn't match live*

I got tired of EAs that look amazing in the strategy tester and then bleed money live. So I built a tool that measures what's actually going on between clicking "trade" and getting a fill.

*ExecutionEdge Analyzer* — free, open-source MT5 EA. Places tiny test trades (0.01 lot, ~$2-6 total) and generates a detailed PDF/HTML report.

The report shows you things you can't see from your trade history alone.

Moderator, this is not self-promotion, trying to help other traders out there, this is free, here is the Ex5, as well as the Source code. 

Files:
 
JSJTradeworx:

the ex5 will be deleted by moderators, and it is strict condition that only source codes will be allowed on the forum.
 
Michael Charles Schefe #:
the ex5 will be deleted by moderators, and it is strict condition that only source codes will be allowed on the forum.
Thanks I did not know that, I deleted the EX5. 
 
JSJTradeworx:
Find out why your EA's backtest doesn't match live*

I got tired of EAs that look amazing in the strategy tester and then bleed money live. So I built a tool that measures what's actually going on between clicking "trade" and getting a fill.

*ExecutionEdge Analyzer* — free, open-source MT5 EA. Places tiny test trades (0.01 lot, ~$2-6 total) and generates a detailed PDF/HTML report.

The report shows you things you can't see from your trade history alone.

Moderator, this is not self-promotion, trying to help other traders out there, this is free, here is the Ex5, as well as the Source code. 

Interesting idea, I like the focus on measuring actual execution instead of just relying on backtests.

Quick question, how long does it usually take for the PDF/HTML report to be generated? I can imagine that depending on the EA or market conditions, some might take longer than others.

Also, just a thought (I could be wrong here), but if you upload it to the CodeBase (in mql5 https://www.mql5.com/en/code) as well, it might reach more people and be easier to find for others who could benefit from it.

Either way, appreciate you sharing this 👍

MQL5 Code Base
MQL5 Code Base
  • www.mql5.com
MQL5 Source Code Library for MetaTrader 5
 

Unfortunately a one time snapshot does not mean much. You have to constantly monitor slippage and execution based on actual trading. There are wel documented cases where one of the "grade A" brokers mentioned in the source code put traders in the to screw over group. 

You can monitor slippage and execution from the actual trading history (MT5 only) without the need for spending money on bogus trades with small lots which might not even reperesent anything close to actual trading. The tool can be downloaded here https://www.mql5.com/ru/code/18801 and explanation can be found here https://www.mql5.com/ru/blogs/post/748959

 
Enrique Dangeroux #:

Unfortunately a one time snapshot does not mean much. You have to constantly monitor slippage and execution based on actual trading. There are wel documented cases where one of the "grade A" brokers mentioned in the source code put traders in the to screw over group. 

You can monitor slippage and execution from the actual trading history (MT5 only) without the need for spending money on bogus trades with small lots which might not even reperesent anything close to actual trading. The tool can be downloaded here https://www.mql5.com/ru/code/18801 and explanation can be found here https://www.mql5.com/ru/blogs/post/748959

I will beg to differ here, if your TP and SL latency are not the same, then this is a disadvantage for you as the trader. This analyzer measures latency in execution from broker side as well. 
 
JSJTradeworx #:
I will beg to differ here, if your TP and SL latency are not the same, then this is a disadvantage for you as the trader. This analyzer measures latency in execution from broker side as well. 
There is no reason to beg and no reason to disagree. If you would have taken the time to read the blog post, you would know we are tlking about the same issue. My point is, you can have the same data your tool generates directly from your own actual trading history including slippage and execution times. 
 
JSJTradeworx:
Find out why your EA's backtest doesn't match live*
My EA's backtest allways match live .
 
Ioannis Christopoulos #:
My EA's backtest allways match live .
Then you must have calculated your average live spread, slippage, and latency, and input them into the Tester. Well done.