Testing

Introduction

This information is provided at the beginning of testing in EWC. We will adapt and extend it as we go along. This means that not all areas are covered yet, mostly because we haven’t had the time yet, but also because we want to test the early set up and be flexible about changing it as we go along.

In EWC there will be a lot of testing and piloting. We will be testing technology, compliance to standards and interoperability, functionality and safety. This will be done across the ecosystem – against platforms, validators/simulators but mainly against each-other.

We will actively test most of the roles in the ARF ecosystem.

In the call for the LSPs and the proposal, it is mentioned that services must eventually be deployed in pre-production.

Types of tests in EWC

We roughly have 4 types of testing in EWC with different purposes:

1. Connectivity-testing Can we reach each other? This test verifies that every service is reachable and is the first step in “activating” a service. It will run continuously throughout the project and involve all operational participants.
2. Interoperability-testing
   Verify that our services work together with the wallet. This will test the implementation of the protocols and standards in the various services when executing the scenarios. Next to basic functionalities, testing will be based on the business scenarios from WP2 and WP3 and cover all requirements from the ARF (Type I) and additional requirements from the EWC scenarios (Type II).
3. End-user piloting
   Do end-users understand what we built and how to handle our services? We will test various scenarios and transactions in 3 planned phases, based on maturity.
4. Security and privacy assessments We need to ensure quality, compliance and protection on our services.