Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • conduct appropriate testing and obtain the relevant certifications (as set out below) prior to ‘go-live’ for each version of the Standards they implement;

  • when testing and obtaining certifications in a Pre-Production Environment, warrant that their Pre-Production Environment mirrors their Production Environment, having the same architecture, network elements, software versions and customer experience elements.;

  • conduct this testing and obtain a separate complete set of certifications for each brand/application, e.g.

    • for LFIs, in cases where the LFI has a number of brands and/or customer segments, each with separate web or mobile apps; or

    • for TPPs, in cases where the TPP has more than one end customer facing web or mobile application;

  • conduct penetration testing (as required below) using a reputable independent third party company.

LFIs and TPPs may conduct stress testing (as required below) using their own internal resources and tools.

LFIs must:

  • conduct Functional Testing (using Ozone Connect Test Suite and Postman Collection) in their Pre-Production Environment prior to promotion to Production Environment and again prior to go-live;

  • submit and obtain CX Certification for their web and/or mobile applications prior to prior to promotion to Production Environment;

  • perform penetration and stress testing (to meet all NFRs in the Standards) before go-live; and

  • engage with TPPs to conduct Live Proving immediately after promotion to Production Environment before go-live.

...