Tenant Onboarding Tests

For testing a tenant integration with the Fibre Cafe, the tenant can be setup on the CVT test environment - as multiple "tenants" if required. This environment supports a number of different mock supplier "stubs" that mimic different suppliers and support a variety of different test scenarios. Where the supplier supports it, their test system can also be configured for testing directly with the supplier.

Supplier Stub Scenarios

By default, the supplier stubs allow for tenants to test the full end to end happy path of Orders (checking availability, appointing and placing an order through to completion) and T2R (completing a service test, raising a service problem), including any update KCIs. Using request headers, the simulation can be tailored to cover various scenarios.

Headers

  • X-Scenario
  • X-Problem-Code (Default: UNKNOWN_FAULT)
  • X-Kci-Delay (Default: 30) (seconds)

How to use

When creating an entity (i.e. Service Order, Problem, Test) or a cancellation or amendment to an entity, scenarios can be used to change the outcome. X-Scenario can be set to any of the allowed values to trigger these behaviors.

If the scenario involves a problem e.g. when dealing with cancellations or delays, X-Problem-Code can be set to any of the available SI problem codes and that will be used in KCIs.

Customising Responses

It is also possible to customise some parameters for the selected scenario by passing in parameters to the header field. For example, you may with to customise the targetDate in the response - for this you can use the targetDateOffset parameter in the X-Scenario header.

Syntax

Copy
Copied
X-Scenario: <SCENARIO_NAME>?<PARAM_NAME>=<VALUE>
  • <SCENARIO_NAME> : The name of the scenario (e.g. ORDER_REAPPOINTED ).
  • <PARAM_NAME> : The parameter you want to set (e.g. targetDateOffset ).
  • <VALUE> : The value for the parameter (e.g. number of days).

You can chain together multiple parameters if needed, using the same syntax as URLSearchParams