Requirements Verification

Verify requirements compares complete generated MQL5 source with the behaviour explicitly requested in the project. Use it after a new build, several modifications or the final stage of a plan. It identifies implemented, partial or missing rules and items requiring manual tests.

The audit reviews source without rewriting it. It is separate from compilation and execution. A file can compile while omitting a session filter, and a filter present in source can still need a test of its broker-time boundaries.

Review the requirements

Open the action on the response you want to audit and inspect the requirements in the dialog. The check uses the complete source associated with that response, so choose the intended revision. Remove obsolete instructions and clarify rules that changed during development.

Use measurable wording, such as “one entry per completed crossover and no new entries after 17:00 broker time”. Include exceptions, such as whether existing positions remain managed outside that session. Verification uses a supported selected model and consumes AI credit.

Read the evidence

Implemented items should refer to relevant code, while partial and missing items explain gaps. Read the explanations as well as the overall result. Risks concerning repainting, orders or dependencies can need attention even when listed features appear implemented.

Source inspection cannot prove broker fills, custom indicator output or historical tick behaviour. Complete those manual tests in MetaTrader rather than asking the audit to certify an outcome for which it has no execution evidence. Keep the results with the tested source.

Repair confirmed omissions

Repair missing requirements prepares a focused request from the audit and reviewed requirements. Read it before proceeding, particularly if the project changed direction. Keep a tested snapshot to compare with the returned file.

Compile and test the revision, then rerun verification when useful. If a repeated finding remains unchanged, clarify the rule or provide its missing dependency instead of repeating repairs indefinitely. Use Existing EA for compiler failures and Testing Expert Advisors for execution checks.