Connect/Logon

This series of tests covers the initial connection to the MFClient and MFAPI Server followed by ungraceful disconnections initiated by MF.

StepActionExpected ResultResult (if different
from expected)		Sign Off
1Client connects (no market data/trading
subscription) to MF		MF confirms client is connected;
client confirms the successful
connection		 
  •  
2MF forces client to disconnectClient is successfully disconnected
and able to reconnect		 
  •  
3MF disables and re-enables API connectionClient is successfully disconnected
and able to reconnect		 
  •  
4Client disconnectsMF confirms client is not connected 
  •  


Heartbeating

StepActionExpected ResultResult (if different
from expected)		Sign Off
1Client connects (no market data/trading
subscription) to MF		MF confirms client is connected;
client confirms the connection		 
  •  
2Client confirms receipt of heartbeat
messages from MFAPI Server		MF confirms heartbeat interval setting 
  •  

In the Classic API, the API Server will send the API Client a heartbeat message every 50 milliseconds
regardless of other activity.

 

 

Logout/Graceful Disconnect

This series of tests covers the logout process and the graceful disconnection from the starting point of an already connected MFClient session

StepActionExpected ResultResult (if different
from expected)		Sign Off
1Client connects (no market data/trading
subscription) to MF		MF confirms client is connected;
client confirms the connection		 
  •  
2Client subscribes to EUR/USD form one
feed any feed (market data/trading)		Client receives subscription enabled
snapshot, followed by incremental
market data		 
  •  
3The Client will end their subscription to
(market data/trading)		MF to confirm the Client is no longer
subscribed		 
  •  

Customer Application should call MFClient.stop(). The corresponding run() invocation will exit with the appropriate
status code.

4The Client will end the session and logoutMF to confirm that the Client is no longer
logged in or connected.		 
  •  

 To disconnect from the MFAPI server, the Customer Application should call MFClient.close()

 

Dropped Connection/Recovery

Venue Disconnect - Client detection

Client Disconnection - MF/venue response.

StepActionExpected ResultResult (if different
from expected)		Sign Off
1Client connects (no market data/trading
subscription) to MF		MF confirms client is connected;
client confirms the connection		 
  •  
2Client subscribes to EUR/USD form one
feed any feed		Client receives subscription enabled
snapshot, followed by incremental
market data		 
  •  
3MF stop the FeedServer, to disable the
venue connection		Client detects venue disconnection
but remains connected to the MFClient		 
  •  
4MF start the FeedServer, to enable venue
connection		Client is now able to view the feed as
available and subscribe to market data
on EUR/USD from the same feed.		 
  •  

Subscription method can be manual or using sticky subscription as described in the user manual.

Sequence Number Scenarios

Seq Num higher than expected (i.e. gap) from both perspectives. Replay requests for missing messages.

Seq Num lower than expected from both perspectives.