EA Generation

Prepare your EA before the Strategy Tester run.

Strategy Tester is not a code review tool. Before running it, make sure the EA compiles, has sensible inputs, logs block reasons, and can produce enough trades to evaluate.

Search intent

The user has a draft EA and wants to avoid wasting Strategy Tester runs.

Paste compiler errors / Generate EA draft / Get risk check

Short opt-in only. We store one source, one intent, and one new lead status. No scraped lists, no purchased contacts, no trading promises.

I agree to receive Workfusion EA builder updates and understand I can unsubscribe later.

Choose the workflow you want, then opt in so the CRM source is measurable.

Run compile and static checks

A clean compile is the entry ticket. Then check for template leftovers, missing trade calls, and missing risk controls.

No TODO placeholders

OnInit and OnTick present

Trade execution path present

Set a test matrix

Use a small test first, then expand. A failed one-week test is cheaper than a failed five-year run.

Smoke test

One month

Three months

Walk-forward review

Capture report context

Save the set file, date range, model, symbol, spread assumptions, and result report together.

Report path

Set file name

EA version

Data model

Use the tool

Run Workfusion compile and readiness checks before launching your next Strategy Tester batch.

Send me the EA workflow Open related tool page

Related guides

Continue the EA build path.

Code Review

MT5 EA backtest failure triage

Classify MT5 backtest failures by compile, data, permission, frequency, execution, risk, or strategy issues.

Code Review

MQL5 code review before backtesting

Review lifecycle, execution, risk, inputs, and logs before spending time on MT5 Strategy Tester runs.

Code Review

Expert Advisor project handoff checklist

Package EA code, set files, reports, assumptions, and risk notes so another developer can review or continue the project.