Testing CTP Order Controls and Market-Status Errors in VeighNa

Summary

This VeighNa community thread discusses gathering evidence for a broker's production CTP account application. The requested checks include counting submitted and canceled orders, confirming that an order with an invalid price increment is detected and rejected, and receiving and displaying a market-status error code. A respondent says the first two checks can be viewed in the risk-control module, while the market-status case was not immediately found. Another participant points to a code change for reference, and the original poster reports testing a market-status response by submitting an order after the close.

The exchange is practical but brief: it does not document the exact code changes, broker response codes, environment, or whether the screenshot requirements were fully met. Participants discuss whether sending an order outside trading hours triggers the relevant error, but the thread supplies no systematic test matrix or confirmation across interfaces. It is best read as a troubleshooting lead for validating order handling, not a complete CTP testing procedure.

Key ideas

• The application checks cover order and cancellation counts, price-increment rejection, and market-status errors.
• The thread says order counts and invalid-price checks are available in the risk-control module.
• A participant reports testing a market-status response by sending an order after market close.
• The discussion links to a code change as a possible implementation reference.
• The thread does not verify a complete procedure or establish behavior across brokers.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.