Test Participant Support

We provide support to several different categories of test participant including:

  • SEC Parties, such as Supplier Parties and Network Parties, that want to conduct User Entry Process Tests and SMKI and Repository Entry Process Tests and become Users
  • Organisations that want to test the interoperability of devices against the DCC such as device manufacturers, test houses and energy suppliers
  • Users that want to test their back office systems against the DCC

We will provide a test environment during the Pre-UIT stage to enable test participants to confirm that they can send and receive messages across the User Gateway. The manner in which the Pre-UIT environment can be used will set out the Guide for Testing Participants.

We have developed a test tool, called GBCS Integration Testing (GIT) for Industry (GFI), to support the development and testing of meters.

User Entry Process Tests and SMKI and Repository Entry Process Tests can be conducted in the Interface Testing stage, End-to-End Testing stage and Enduring Testing phase.

Test Participants can use the CSP Test Labs or a Remote Testing Service (subject to meeting entry criteria) to test the interoperability of their devices and back office systems against the DCC.

As part of the consultation in June 2015, on the first part of the Enduring Testing Approach Consultation, DCC proposed a set of limits relating to the Certificate Signing Requests that Testing Participants may submit and the number that DCC shall be obliged to process.
These limits are set out in the table below:

Limits for submitting Certificate Signing Requests for testing                                              
Each Testing Participant shall not submit more than 25,000 CSRs per day.
DCC shall not be required to process any Certificates Signing Request (across all SMKI interfaces) in excess of 100,000 (and not 375,000) per day. Certificate Signing Requests exceeding this number shall be queued for processing as soon as reasonably practicable.
If a Testing Participant foresees a need to submit in excess of 12,500 Device Certificate Signing Requests through the SMKI Portal interface in any 24 hour period, the Testing Participant shall use reasonalbe endeavours to inform the DCC of the potential additional load at least seven days in advance via the DCC Service Desk. The Batch or Batches exceeding this number shall be queued for processing as soon as reasonably practicable.
Each Party shall use reasonable endeavours not to submit more than one CSR via the Ad Hoc Device CSR Web Service interface in amy 1.6 second period (and not 0.8 second period).

DCC will advise in the event that these limits are revised.

Documents

Guide for Testing Participants

DCC is publishing the Guide for Testing Participants. The document is required to describe which persons are eligible for which Testing Services, and on what basis (including any applicable Charges). This version of the guide also provides clarity and helpful information regarding aspects Transitional Testing.

Guide to SMKI and Repository Entry Process Tests

The Guide to SMKI and Repository Entry Process Tests sets out the information that a Party is required to provide in support of its application to complete the SMKI and Repository Entry Process Tests (SREPT).
This document provides further explanation of the testing approach set out in the SMKI and Repository Test Scenarios Document.

Successful completion of the SREPT is a requirement before a Party or RDP is entitled to:

(a) apply to become an Authorised Subscriber for the purposes of any Certificate Policy; or
(b) access the SMKI Repository.

 

End-to-End Testing Approach Document  v3.11

Version 3.11 of the End-to-End Testing Approach Document was approved by the SEC Panel on 8 July 2016. DCC is publishing the document in accordance with Section T4.9 of the SEC.

Guide for Testing Participants (pre-UIT version) 

This guide has been published as a working document for Testing Design and Execution Group members and it will be updated to accommodate comments and re-published on the website.

Related Documents

End-to-End Testing Approach