Guys, I am still developing this. If I share this now i have to explain my stretegy as well. At the moment I cant do that.
I can understand what you trying to say. THIS IS NOT ONE MINUTE CHART. This is strategy is based on renko charts. To backtest I have imported renko chart history on EURUSD one minute chart.
what timeframe are you testing it on? if you can replicate that in demo then you should be golden.
my only suggestion for the variable lot size would be to use the stair method. basically the EA can only increase lot sizes and never decrease them. so if it is trading for example 3 lots that becomes the new minimum and it will keep trading 3 lots until it moves up to 4 lots.
If the EA will perform similar live then you have a nice steady EA. Gratz on that.
There are some points of concern that you may have to consider:
The test quality is 25%. Often this can be due to missing tick data that, when it would be available, could have caused premature trade exits. For example, did you derive your data from actually tick data or did you just use the bars available in your history for lets say the 15 min chart (that does not include the intermediate ticks). Consider this may reulst in a lower performance on a live account.
Please consider that you may have unconciously made an EA that performs specifically for this test period. It is not uncommon that someone writes an EA that works well in their test period (I am guilty to when I started developing scripts). It is an excellent way to learn hw important details are, but don’t throw in your live-saving in the game just yet.
Considering the consistent growth I have some concerns how you EAs deals with scheduled news events. Did you work your way around it or does it obtain such information from external sources? Have you been seriously unbiased with your EA in dealing with such events, or did you incorporated some ‘workarounds’ that applies to your testperiod.
The tester doesn’t consider executions issues. Considering the very thight SL and TP any delays in execution (for example due to a low ping) can give you poorer execution than your tester. Keep that in mind to.
That is all I can think of at the moment (not knowing your strategy or having seen your script). I hope it has any use for you.