Dark order and alert clearing tests #466
Labels
accounting
prolly positioning: the accounting of "what/when (is) owned"
clearing
auction and mm tech: EMS, OMS, algo-trading
ledger
trade, accounts and other user focal event history tracking, management and storage
testing
In follow up to #462 and in relation to #463 we need to add a similar test set as is landing in #462 but for both dark (triggered) orders and alerts.
The main difference will be that we need to have the test harness also load a data feed to as to submit the darks orders close to the current L1 spread to ensure we trigger and clear.
Testing ToDo:
trade_stream: tractor.MsgStream
matches expected flow and eventual positioning stateThe text was updated successfully, but these errors were encountered: