The following tables list each version of the Conformance Test Suite (CTS) commencing at v2.0.0 providing detail on the version of the Consumer Data Standards and CDR Register Design Reference it aligns with, the release date, the test scenarios included, and the high level scenario changes between versions. When new test scenarios are added, they are added to the existing list and identified with an asterisk.
More information on these scenarios is available in the CTS Guidance Materials article.
CTS version |
Applies to |
Release date |
3.4.0 - Flexible test plan | Data recipient | 30/03/2022 |
3.4.1 | Data holder | 20/01/2022 |
3.4.0 | Data holder and data recipient | 09/09/2021 |
3.3.0 | Data holder and data recipient | 30/07/2021 |
3.2.0 | Data holder and data recipient | 17/06/2021-01/07/20211 |
3.1.0 - OBSOLETE | Data holder and data recipient | 29/04/2021 |
3.0.0 - OBSOLETE | Data holder and data recipient | 08/04/2021 |
2.1.0 - OBSOLETE | Data holder and data recipient | 18/03/2021 |
2.0.0 - OBSOLETE | Data holder and data recipient | 18/02/2021 |
CTS Data Recipient Version: 3.4.0 - Flexible test plan
Released on: 30/03/2022
CDS |
Register Design |
# Scenarios |
Version changes |
Data Recipients – Flexible Test plan - 1 Scenario, 4 core competencies.
|
Released on 30-Mar-2022 After the ADR has been activated in the CTS ecosystem, CTS waits for the ADR to engage on 4 core competencies to determine if the ADR’s software product can conform to the CDS and the Register Design. The 4 test competencies can be completed in any order. |
CTS Data Holder Version: 3.4.1
Released on: 20/01/2022
CDS |
Register Design |
# Scenarios |
Version changes |
1.10.0
|
1.5.0
|
Data Holders - 17 scenarios
|
Released on 20-Jan-2022 No New Scenarios Updates on CTS Register endpoints to be consistent with CDR Register endpoints, no operational process change. Details of CTS Register endpoint changes are listed in the CTS Guidance Material:
Updated DCR endpoint – from CTS CDR Register via JWKS Endpoint to CTS CDR Register via the SSA JWKS Endpoint |
CTS Version: 3.4.0
Released on: 09/09/2021
Download guidance for data holders
Download guidance for data recipients
CDS |
Register Design |
# Scenarios |
Version changes |
1.10.0
|
1.5.0
|
Data Holders - 17 scenarios
|
Released on 09-Sep-2021 No New Scenarios CTS Test Scenarios have been updated to validate the usage of standardised Error Codes, where Participants have started adopting the Standardised Error Handling requirements, as per CDS 1.10+. Where the Participant has adopted the Standardised Error Handling Requirements, CTS will validate that their responses for specific CTS induced failure conditions (e.g. invalid Software Product, Invalid Consent etc.) conform to CDS 1.10+ requirements - which includes validation of HTTP Status Codes, Error schema and the usage of correct Standard Error code itself. Where Participants have not started using the standardised Error codes in their responses, the CTS validation will revert to the existing logic as per Test Plan 3.3. |
Data Recipients - 9 scenarios
|
Released on 09-Sep-2021 No New Scenarios CTS Test Scenarios have been updated to validate the usage of standardised Error Codes, where Participants have adopted the Standardised Error Handling requirements, as per CDS 1.10+. Where the Participant has adopted the Standardised Error Handling Requirements, CTS will validate that their responses for specific CTS induced failure conditions (e.g. InvalidArrangement etc.) conform to CDS 1.10+ requirements - which includes validation of HTTP Status Codes, Error schema and the usage of correct Standard Error code itself. Where Participants have not started using the standardised Error codes in their responses, the CTS validation will revert to the existing logic as per Test Plan 3.3. * Scenarios 8 and 9 are considered optional for data recipients in line with CDS 1.11.1 |
CTS Version: 3.3.0
Released on: 30/07/2021
Download guidance for data holders
Download guidance for data recipients
CDS |
Register Design |
# Scenarios |
Version changes |
1.10.0
|
1.5.0
|
Data Holders - 17 scenarios
|
No new scenarios
*Phase 2 consumer data will be sourced from the following end points: Get Account Detail, Get Direct Debits for Account, Get Bulk Direct Debits, Get Direct Debits for Specific Accounts, Get Scheduled Payments for Account, Get Scheduled Payments Bulk, Get Scheduled Payments for Specific Accounts, Get Payees, Get Payee Detail, Get Customer Detail
|
Data Recipients - 9 scenarios
|
No new scenarios
* Scenarios 8 and 9 are considered optional for data recipients in line with CDS 1.11.1 |
CTS Version: 3.2.0
Released on: 17/06/2021-01/07/20211
CDS |
Register Design |
# Scenarios |
Version changes |
1.8.0 |
1.5.0 |
Data Holders - 17 scenarios
|
1Released on 17/06/2021 No new scenarios. Each scenario has been modified to be compliant with the following two Register design changes described in Release notes v1.5.0:
Testing related to the “request_object_signing_alg” may be considered at a future date.
One user to many brands The CTS implemented a feature which will allow users with the ‘Authorised CTS Tester’ role in the RAAP to access all CTS instances under their organisation(s) e.g. brands. When the user logs into the CTS participant UI, they will be able to pick a brand or software product from the CTS user interface, and they will be navigated to that instance. 2 |
Data Recipients - 9 scenarios
|
1Released on 01/07/2021 No additional scenarios Modifications have been made to be compliant with the following two Register design changes described in Release notes v1.5.0:
One user to many software products The CTS implemented a feature which will allow users with the ‘Authorised CTS Tester’ role in the RAAP to access all CTS instances under their organisation(s) e.g. brands. When the user logs into the CTS participant UI, they will be able to pick a brand or software product from the CTS user interface, and they will be navigated to that instance. 2 |
2 NOTE: the 'Authorised CTS Tester' role will have access to all CTS instances for that organisation, and any other organisations they are assigned to. Access is not limited by brand. This aligns to the user roles and permissions matrix available in the participant portal user guide.
CTS Version: 3.1.0 - OBSOLETE
Released on: 29/04/2021
CDS |
Register Design |
# Scenarios |
Version changes |
1.8.0 |
1.4.0 |
Data Holders - 17 scenarios
|
Three new scenarios* |
Data Recipients - 9 scenarios
|
No additional scenarios Support for Sector Identifier uri (optional field from Register design) |
CTS Version: 3.0.0 - OBSOLETE
Released on: 08/04/2021
CDS |
Register Design |
# Scenarios |
Version changes |
1.7.0 |
1.3.0 |
Data Holders - 14 scenarios
|
Two new scenarios* ^Conducts suite of bad requests against the token endpoint, to test error returned from DH |
Data Recipients - 9 scenarios
|
No additional scenarios |
CTS Version: 2.1.0 - OBSOLETE
Released on: 18/03/2021
CDS |
Register Design |
# Scenarios |
Version changes |
1.7.0 |
1.3.0 |
Data Holders - 12 scenarios
|
No new scenarios However support for Register design 1.3.0 (new optional fields in the registration request, plus additional new OpenID scope) |
Data Recipients - 9 scenarios
|
No new scenarios However support for Register design 1.3.0 (new optional fields in the registration request, plus additional new OpenID scope) |
CTS Version: 2.0.0 - OBSOLETE
Released on: 18/02/2021
CDS |
Register Design |
# Scenarios |
Version changes |
1.6.0 |
1.2.3 |
Data Holders - 12 scenarios
|
Initial release for Non-Major ADIs |
Data Recipients - 9 scenarios
|
Initial release |
Comments
0 comments
Please sign in to leave a comment.