|
|
|
The Strategy Tester in the trading platform allows you to test not only Expert Advisors but also indicators. This can be done in the visual testing mode. The behavior of the indicator is shown on a chart, which is plotted based on a sequence of ticks simulated in the tester.
|
Various indicators are available in the MetaTrader Market. Before purchasing you can download a demo version of an indicator and test it in the strategy tester.</s2> |
This section describes how to configure and test indicators.
Setup
- How to Select an Indicator and Configure It
- Symbol and Its Period
- Modeling Techniques
- Time Range
How to Select an Indicator and Configure It
If you need to test an indicator, select the appropriate program type "Indicators" in the strategy tester. After that, select an indicator from the list. The list features all indicators, which are located in the terminal folder MQL4\Indicators (including subfolders).
|
When you select testing of indicators, the visual mode is automatically activated. |
You can test any indicator from the Market for free before buying. Download the demo version of the indicator, double-click on it in the Navigator, and click on "Test":
Then the indicator will be selected in the strategy tester, you will only have to configure parameters and start the testing process.
If an indicator has any input parameters, you can configure them before the start of testing. Click "Indicator Properties".
Symbol and Its Period
To start testing, it is not enough just to select an indicator and set it up. One has to select a symbol and a period (timeframe) for testing. These are data that will be used for testing. At testing, one can select an available terminal symbol or use an external data file. History data files of *.FXT format stored in the /TESTER directory are used in testing. These files are created automatically at testing if an available in the terminal symbol was selected.
The symbol is defined in the field of the same name and timeframe is in the "Period" field. If no data file for this symbol, period, and modeling method does not exist yet, it will be created automatically. If there are no history data for the symbol or period, the tester will download the last 512 history bars automatically.
|
Attention: If there are some data outside the latest 512 bars for the symbol, the history data will be downloaded automatically, up to the last available one. This can cause a sharp increase in incoming traffic. |
Modeling Techniques
Historical data are saved in the terminal only as bars and represent records appearing as TOHLCV (HST format). These data can be used for modeling price changes at testing indicators. In some cases, such information is not enough for testing. For example, for the daily timeframe, price changes within a bar can result in generating a trade signal. At the same time, no generation may occur at testing. In other words, testing an indicator based on only bars can be inaccurate and give a false idea about the efficiency.
The trading terminal allows the testing of indicators by various methods of historical data modeling. Using historical data from smaller periods, it is possible to see price fluctuations within bars, i.e., price changes will be emulated more precisely. For example, when an indicator is tested on one-hour data, price changes for a bar can be modeled on one-minute data. Thus, modeling brings historical data near the real price fluctuations and makes expert testing more authentic.
One of three methods of historical data modeling can be chosen for testing:
- Open prices only (fastest method to analyze the bar just completed)
- Control points (the nearest less timeframe is used)
- Every tick (based on all available least timeframes)
|
Find out more about modeling techniques in the section "Testing Strategies". |
The price history stored in the client terminal includes only Bid prices. On default, to model Ask prices, the strategy tester uses the current spread of a symbol at the beginning of testing. However, a user can set a custom spread for testing in the "Spread" field.
Time Range
The range of dates allows testing experts not on all available data, but within a certain time-space only. This can be useful if there is a need to test a certain part of history data. The date range can be used not only for expert testing but also for modeling of the testing succession of bars (file of data modeled to be used for testing).
It is often no need to model data of the entire history, especially for every-tick modeling where the amount of unused data can be very large. That is why, if data range was allowed to be set at the initial modeling of testing succession, bars that are beyond this range will not be modeled, but just transcribed into the output succession. The data will not be excluded from the succession in order for the correct calculation of indicators on the entire received history to be possible.
It must be noted that the first 100 bars will not be modeled either. This limitation does not depend on the date range defined.
To enable date range limitation, one has to flag "Use date" and specify the necessary values in the fields of "From" and "To". After all, settings have been made, one can press the "Start" button and start testing. After testing has started, the approximate time of completing this process can be viewed in the lower part of the window.
Indicator Testing Process
The behavior of the indicator is shown on a chart, which is plotted based on a sequence of ticks simulated in the tester. This chart is generated automatically after the testing process is started. Its name contains the financial symbol, the timeframe used, and the property "visual".
Logs on the indicator testing process appear n the "Journal" tab. This journal is similar to that in the "Terminal — Experts" window. The only difference is that in the tester window, logs are related to the indicator testing instead of operation on a real chart. After the testing process is over, these data are displayed in a separate directory /TESTER/LOGS. The log files are stored in folder /EXPERTS/LOGS, file names correspond to journal creation date — YYYYMMDD.LOG.