The Lab

Introduction

MarketFactory Customers access the trading venues of their choice by integration with Whisperer via the Java, C++ or C# MFAPI, or by direct integration to the SBE messaging layer.

All new clients are assigned a UAT environment in which they may develop their own application against Whisperer and the individual Venues.

Once this stage of the process has finished, the client will be required to participate in a Certification Test with MarketFactory which must be completed successfully in order for the client to move into the production Whisperer environment. Additional Certification Tests may be required by individual Venues.

MarketFactory expects Clients to have performed their own Quality Assurance (QA) testing prior to the certification scenarios listed on this page.

MF Certification

The MarketFactory Certification process is designed to ensure both Customer and MarketFactory systems integrate at a functional and non-functional level to an acceptable standard, so that both parties are confident that go-live can proceed. 

Certification Sign-off is required by the Client's project/business sponsor responsible for the integration to MarketFactory.

Once clients are live in the production environment, there may also be a requirement occasionally for re-certification, as described below.

Venue Certification

Even though MarketFactory may have fully implemented a given Venue's API and successfully onboarded many Customers previously, some Venues will mandate that each new Customer be subject to their own Certification Tests. In such situations, these will be organized by MarketFactory and conducted using three-way conference calls to coordinate actions.

Recertification

The need for re-certification testing will be decided on a case by case basis, but generally will be required in the following circumstances:

  • If MarketFactory needs to make changes to their server-side infrastructure that could impact the Customer.
  • If live clients need to make changes to their application or to their infrastructure, which could impact MarketFactory or Venue processing.
  • If the connectivity method between MarketFactory and the Customer changes in any way
  • If MarketFactory, the Customer or a Venue should decide that there is a need to conduct a re-certification.


Schedule

A schedule to cover Certification or Re-certification testing will be agreed between MarketFactory and the Customer. Sufficient time will be allowed in this schedule so that the testing can be completed prior to the planned go-live date. In the case of re-certification where changes have been made by MarketFactory to our systems, adequate time will be allowed for clients to also make changes and re-test with us. However, for some types of change, MarketFactory may only be able to continue to support older configurations or versions of the interface for a limited time.


Scope

Certification testing will generally cover the areas listed below. Any exclusion to this must be agreed between MarketFactory and the Customer prior to the Certification Test. Conversely, in other cases it may be necessary to agree and execute additional tests - for example, where the client application relies on custom functionality or features. 

Recertification, when required, may not need to include all the areas required for initial Certification, in this case, coverage will be  agreed between MarketFactory and the Customer on a case by case basis.


  • No labels