Discussion of article "The checks a trading robot must pass before publication in the Market" - page 9

You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
How to solve this problem? Trades are opened in the regular tester.
How to solve this problem? Trades are opened in the regular tester.
It does not say that trades are not opened. It says that the robot takes too long to trade - the autotester hints that you need to speed up the code.
Lack of report is usually a glitch of the autotester, it can be cured by retesting after some time, but it can be caused by the first reason.
It does not say that trades are not opened. It says that the robot takes too long to trade - the autotester hints that you need to speed up the code.
Lack of report is usually a glitch of the autotester, it can be cured by retesting after some time, but it can be caused by the first reason.
I see, that's what I thought. It's strange that the same code for mt5 passes without problems, but on mt4 it doesn't want to.
- The question is simple: Why can't we make it possible to set restrictions for the demo versions of the product? If MQL5 Market cares so much about users: "All such actions (any restrictions in operation) will be regarded as unfriendly to the Buyer and are unacceptable." - then from the user's point of view, it is easier to take a free demo version with restrictions on asset type, timeframe, etc. and test it on a live chart.
To let the user evaluate, you can make a demo and attach it to the product.
And Autovalidator has never swore at limitations of work for demo only.
At the same time, I find on the market products, demo-versions, which have passed this very auto-check, for the presence of restrictions:
What is the secret of selectivity? )
At the same time I find on the market products, DEMO-versions, which have passed this very auto-check, for the presence of restrictions:
What is the secret of selectivity? )
The secret is simple:
It says: It is forbidden to build restrictions into the product.
And the demo version in the product is a demo for a tester (such a calamity with names, although now it is a trial)
And the demo version is a real demo version that works for free on a demo account.
And so that you don't ask questions:
How to check it on the real account?
There is a restriction on a real account only for the USDJPY pair
No selectivity.
Autovalidator has never swore at demos.
But restrictions in the paid version, like MAKS LOT (and paid version), it is forbidden.
A demo can be made and attached to the product for the user to evaluate.
And Autovalidator has never swore at limitations of work for demo only.