How to write a development brief for a cTrader cBot
A checklist for commissioning a custom C# cBot, including bar events, volume in units and acceptance testing.
A useful cTrader Algo brief makes each cBot decision reproducible under specific conditions. Start with a symbol, a timeframe and a few cases the software must handle.
Decide whether the signal uses ticks or closed bars
If a signal needs the last bar’s final values, specify closed-bar evaluation. In cTrader, OnBarClosed() runs when the event opening the next bar arrives. The final bar before a break in ticks may only be reported as closed when trading activity resumes. For intrabar behavior, describe the tick-level rule and what should happen if it triggers several times.
Specify volume and order handling
cTrader Algo supports order volume in units. State whether your inputs are lots, units or a risk formula, and what to do if the result does not match the symbol’s permitted volume increment. Include spread filters, trading hours, position limits and how the bot should respond to a broker rejection.
Select data and acceptance cases for the beta
Record the symbol, data source, spread, commissions and inputs for each backtest. Pick examples you can identify in the cBot’s logs. Include one accepted entry, one signal skipped by a filter and a restart while a position is open.
If the cBot depends on a custom indicator, share the source you can provide or describe its outputs. Specify which value the bot reads and when it becomes final.
See the official cTrader guides on bar events and backtesting a cBot.
