Internal testing / quality assurance DSOP Control Common Standard

To ensure proper technical and functional implementation of the DSOP Control API, including correct interpretation of the API specification, information flow, and data model, the data providers (the financial institutions) must perform and complete all the test cases both in test and production environments. These tests are listed and described in the following document:

DSOP Control Common Standard - Testcase for Data Providers..

Test case categories

• Integration & responses: Tests to be performed in the data providers’ test environment in order to validate the integration with the data consumers, as well as the right implementation of the architecture of the DSOP Control Common Standard.
  
• Validation & expected delivery: Tests to be performed in the data providers’ test and production environments to verify the correct implementation and behaviours of the endpoints in the DSOP Control API.
  
• Data Quality in delivery: Tests to be performed in the data providers’ production environment in order to verify that data delivered from the DSOP Control API is the same as if this information was delivered manually. Any discrepancies or differences should either be corrected or documented.
  
• Deviations & compliance: Checklist to be filled out preferably in advance of a production set-up or during the first few weeks of production.

These tests are designed to help data providers ensure that their implementation of the DSOP Common Standard across the various DSOP services is correct and meets the required standard of quality. The document will have to be shared with Bits as part of quality assurance.

Reporting of deviations and limitations
To ensure that data consumers can correctly understand and use the information received through the DSOP Control API, data providers must report known deviations and limitations in their implementation.

The purpose of this reporting is to make data consumers aware of circumstances where information delivered through the API may be incomplete, unavailable or differ from information provided through manual handling. This enables the data consumer to take known limitations into account when interpreting and processing the received data.

Any known deviations or limitations that may affect the delivered data must be reported in the following document:

DSOP Kontrollinformasjon – Informasjon til etat

The information must be kept up to date. Any changes to the standard or changes originating internally at the data provider that affect how data delivered through the API differs from manual handling must be reported to Bits.

The form must be submitted to Bits via dsop@bits.no

Change log