The primary problem with back-testing is that you may see something that works, but it may only "seem" to work.
Unless you are able to answer the WHY as per your hypothesis, then it is just a coincidence.
Don't look at the data to TRY and find correlation - that will only end in ruin.
You have to have a hypothesis prior to making any test.
Simple example:
1. I believe that X meets X objective when X happens.
2. I believe this happens because of X force.
3. I believe that this event has a probability of x%
Now test for it.
The majority of the back-testers I run across are blindly searching for a connection. They see patterns in everything. That only works if you are able to answer the WHY? Otherwise you are putting the cart in front of the horse.
Also -
If you are not able to clearly answer your expectations of your strategy (risk/reward) than any back-testing is pretty useless. Back-testing should verify a hypothesis and check for statistical results. It should not be used to justify the risk/reward expectation of the strategy. Many forget this simple yet important difference.
I also believe that forward (live) testing is as important. Using a sim-route for execution and keep forward logs will check for execution risk, liquidity, etc.
Unless you are able to answer the WHY as per your hypothesis, then it is just a coincidence.
Don't look at the data to TRY and find correlation - that will only end in ruin.
You have to have a hypothesis prior to making any test.
Simple example:
1. I believe that X meets X objective when X happens.
2. I believe this happens because of X force.
3. I believe that this event has a probability of x%
Now test for it.
The majority of the back-testers I run across are blindly searching for a connection. They see patterns in everything. That only works if you are able to answer the WHY? Otherwise you are putting the cart in front of the horse.
Also -
If you are not able to clearly answer your expectations of your strategy (risk/reward) than any back-testing is pretty useless. Back-testing should verify a hypothesis and check for statistical results. It should not be used to justify the risk/reward expectation of the strategy. Many forget this simple yet important difference.
I also believe that forward (live) testing is as important. Using a sim-route for execution and keep forward logs will check for execution risk, liquidity, etc.