As an active tester, you will have access to a wealth of results provided by a huge number of colleagues. You can drill down to every possible TradeReport and TradeChart for every test and every setup with a few clicks. You can see the most profitable and promising tests of the whole group. You will get all this information for free if you contribute as a tester. A win-win situation as we all will profit from our group efforts.
Backtesting in MT4 has so much limitations that it cannot produce anything reliable. Only forward tests can give you a rough idea of possible results. That is why our project exists. But keep in mind that live results and demo results may differ significantly due to slippage etc. You must understand and agree to our disclaimer.
As a trader, you can best support the project by adding test results of EA setups that are unique. As a coder, you can best support the project by adding your EAs to our panoply of compatible experts. If you want to support and secure the database operation, think about a PayPal donation to firstname.lastname@example.org. In the future, there will also be a special group of early supporters with extended privileges. A donation will help to reserve your seat.
Every system has technical limitations. We will archive non-promising EAs on a regular basis to keep the live database sleek and on a high performance level. Don't worry, we are taking care. We provide enough resources, but if you want to secure them, think about a PayPal donation to email@example.com.
Every system has technical limitations. But we have taken every measure in advance to keep the live database on a high performance level. For example, the data transmissions of the participants are distributed over the last trading hour of each day by a sophisticated algorithm. Then the whole data is cached on the web server for nearly unlimited parallel access. Don't worry, we are taking care. We provide enough resources, but if you want to secure them, think about a PayPal donation to firstname.lastname@example.org.
Exactly the same as you. We will have access to a wealth of results provided by a huge number of colleagues. We can drill down to every possible TradeReport and TradeChart for every test and every setup with a few clicks. We can see the most profitable and promising tests of the whole group. Of course, a lot of our private time and money went into this project. If you want to support us, think about a PayPal donation to email@example.com.
You will always have free access to highly valuable information that is not publicly accessible as long as you actively contribute as a tester. In the future there will also be a special group of early supporters with extended privileges. If you want to reserve your seat, think about a PayPal donation to firstname.lastname@example.org.
You must be an active EA tester and have submitted enough results to the database. This website is a place for forex traders to share their testing results. You can get all information needed to participate on the Infos for Testers page.
You must be an active EA tester and have the connector EA running. Then you can click the highlighted text of the connector EA output to get a pop-up showing your authorization key. This key is automatically copied to the clipboard for your convenience. On the website login page, you have to enter your nickname and paste the key into the appropriate fields. You can generate a key from any of your accounts with active tests. Each of your keys will be valid for the website. But remember, you must have transmitted enough results to get access. Most browsers (if not all) have means to store and later automatically fill input fields. If you have enabled this feature, you will have to enter your credentials only once. There are also password manager plugins that you can use for that purpose.
You must be an active EA tester and install the connector EA. As soon as you have the connector EA up and running, you can click the highlighted connector EA's output text to get a pop-up showing your authorization key. This key is automatically copied to the clipboard for your convenience.
The account nickname/auth key combination will be valid login credentials for the secure part of the FXTestify.com website, provided that you have been supplying your test results for a sufficient number of days (at least 5 days within the last 20 days). This measure has been installed, to avoid people asking for an auth key, merely to be able to login to the site and see other peoples results, without uploading any test results of their own.
We need to normalize results to come to a valid average that weighs all trades in a comparable way and not be influenced by trade size or duration. All results are normalized to show the "result per lot per day", i.e. what would have been the average result for each day had you traded one lot. This needs two calculations. Every trade is recalculated to the size of one lot as not all trades have the same lot size. This is easy. A trade of 0.1 lot gets multiplied by 10, one of 0.01 lots by 100. The overall result over a period of time is divided by the days the observed object (trade/testset/symbol) was running. A trade that makes 1000 units in one day is clearly twice as good as one that makes them in 2 days. In short:
Each trade is re-calculated to one lot.
All trades are summed up.
This sum is divided by the sum of all days on all accounts.
Now lets assume a new EA steps up and has a good first week on a small number of accounts. It will instantly lead the ranks by far, as we don't have many accounts and days to divide the result by. As the new EA is traded over a longer period, it will have good weeks and bad weeks, more traders will join the test and they will have good setups and not so good setups. The results will more and more average and become comparable to the EAs that are already running for a while.
Our main question is: How does an EA perform on the long run if configured properly? We can get an answer if we are testing it long enough and filter out the results of failed setups. That can be done with the four buttons on the top right of the overview page. They will filter and show the results for the best 10/25/50/100 percent of the setups.
Trade results for a certain expert advisor can be aggregated by account or by test set. A given tester's account could have been testing multiple test sets consecutively over time and a given test set could have been tested on multiple accounts. On the other hand, test sets on the same account may be very similar and possibly only differ because the expert provider has added new inputs or changed default settings. In order to evaluate which settings performs best, look first at the account view and then get more details from the test set view.
We treat every distinct combination of account and magic number as "virtual" account. These are what we show on the website as accounts. As we dont want to publish real account numbers, the names are derived from the tester nicks.
The database shows all different configurations (test sets) you have been running over the lifetime of your account. That doesn't mean you have run these test sets at the same time, it might have been in succession. Sometimes EA coders/providers change their parameter/input set. That can result in a different test set although the basic test stayed the same.
Generally it means that one part in the combination of test set value and default value (in parantheses) could not be found. Reason are inconsistencies that occur if the EA provider adds or deletes inputs. If you are testing a newer EA version with an older test set, be especially sensitive to added inputs (unknown default values). They might alter the behavior of the test set and you must possibly disable new features to reproduce the test set results.
Definitely not. We want traders running long term cross bench tests of the EAs with different setups (test sets) on demo and live accounts with different brokers all over the world. The more the setups are diversified, the more reliable they are.
Submitting your results is a task completely controlled by our connector EA. Set up your tests, load the connector EA on a separate chart in every terminal and it will do its work and transfer the needed data to the database every night. Just make sure it is constantly running side-by-side with your tests to submit daily data.
Exactly one for each terminal/account. There is an input "MagicNumbers" in the EA settings. You can leave it at "-1", meaning all trades are submitted. Or you can enter one magic number or a comma-separated list of them to define which trades you want the EA to submit.
The output should have some lines and "Click this text to see your authorization key" as the last one. WARNINGs are ok, but ERRORs or abortion messages indicate problems. The second line shows the actual local time. If this lags more than one minute, the connector must have stopped working. There is a another simple possibility to test whether the connector is running. Click on the last line of text and a popup with a message about your authorization key must appear.
Definitely not. We will be happy if EAs from other sources get added to the system. But EA providers please obey the instructions on the Info for Providers page. And as there is some data to prepare in the database for integrating new EAs perfectly, please contact us before publishing.
We would be happy if you do so. But please obey the instructions on the Info for Providers page. And as there is some data to prepare in the database for integrating new EAs perfectly, please contact us before publishing.
Definitely not. There is no place in our scenario for manual intervention. We are interested in the potential of the experts/setups, not in the trading skills of humans. The results must be reproducible. Please thoroughly read the Info for Testers page.
Of course you can fix bugs and improve things. But please be sensible to the following aspects: If you change the EA inputs, all tests might automatically start from scratch as new tests because the test set has changed. Avoid deleting old obsolete inputs, just leave them there. Also avoid changing the default values for inputs. If you change important parts or add inputs, better consider the expert being a new one and publish it with a different database expert code. This will help you to judge whether your changes really improve results.