Our Emulation Environment - EMMA
The emulation environment (EMMA) is a secure sandpit/emulator environment for you to perform your own B2B evaluation, component and integration testing. EMMA is a mirror image of production code, database structures and is built on the same technology stack as production B2B. EMMA calls on its own instances of the databases. We have built stubs to emulate certain non-customer facing components. The Product catalogue and NADB databases used in EMMA are populated with data from Production or Non-production. This is updated once a year, or more frequently if there are changes that require it. This means that information related to product ID and location statuses should not be assumed to match production.
EMMA is governed by our release management process, ensuring that all production changes will be available in EMMA for testing prior to launch. This will include updates to documentation and database extracts. The current EMMA version is Release 4 with WSDL 3.3.51.
EMMA is not a performance testing environment, but on consultation a test plan can be agreed.
More about the Stubs
We have built 3 stubs to fulfil various functions. This simplifies the environment and the management of test data, while retaining all customer-facing functionality.
> SOM Stub
The SOM stub emulates the backend network components. For orders with no site visits, it controls the speed at which the order progresses to Service Given.
It can also be configured for specific TLCs to enable testing of certain alternate scenarios, e.g. orders failing feasibility.
EMMA will always return SVID : 1001 and CVID : 1000
> HTR Stub
The HTR stub emulates the backend site visit work order components. For orders with site visits, it controls the speed at which the order progresses.
It can also be configured for specific TLCs to enable testing of certain scenarios that can result from site visits in the real world, e.g. orders being rescheduled or held for the customer to reschedule.
> CWMS Stub
The CWMS stub emulates the backend site visit appointment components. Only TLCs which have been specifically configured in the CWMS stub will return available appointment slots. As part of the B2B onboarding process, your Chorus Implementation Manager and Test Manager will work with you to arrange for TLCs to be loaded into the CWMS stub for your testing.
Stub Timings
The table below shows you the time intervals when status changes (and associated notifications) will automatically occur on your orders in EMMA, based on how many site visits are associated with the order. For example, if you place a Connect Primary order at 10:00am and it has both a Scope and Install appointment, you would expect the status to change to In Progress – Scheduled at 10:15am.
Please talk to your Implementation or Test manager to discuss any requirements for alternate scenarios you need to test.
| Time from order acceptance | 2 Site Visits | 1 Site Visit | RFS Date (0 Site Visits) |
| +0m | In Progress - Scoping Scheduled | In Progress - Scheduled | In Progress - Scheduled |
| +10m | In Progress - Scoping Scheduled* | In Progress - Scheduled** | In Progress - Scheduled |
| +15m | In Progress - Scheduled | In Progress - Scheduled** | In Progress - Scheduled |
| +20m | Service Given (cannot reschedule any appointments from this point onwards) | Completed - Billing | Completed - Billing |
| +25m | Completed - Billing | ||
| * from this point onwards you should avoid rescheduling the scope appointment | ** from this point onwards you should avoid rescheduling the appointment |
Chorus Portal EMMA Extract
The Chorus EMMA Portal Extract contains the full list of addresses stored in EMMA Portal, in CSV format. Any information related to product ID and location statuses should not be assumed to match production.
How to use the extract
| Step 1 | Download the CSV file (link) and open in a database (too big to open full CSV in spreadsheet) |
| Step 2 | Filter the CENTRAL_OFFICE column for the exchange that has been assigned to you during onboarding. |
| Step 3 |
Depending on the scenario you are interested to test filter the required columns. For example:
|
Chorus Product Catalogue EMMA extract
The EMMA product catalogue contains both the EMMA product offer ID and the product specifications and characteristic of all on boarded products and CSEs. It is important to know that Product Offer IDs cannot be assumed to match production.
The extract also contains the rules for which product characteristics
- Are required at feasibility and order creation.
- Can be amended during order workflow.
You will need this information during your B2B development of feasibility, create order and amend order.
The extract needs to be used together with the EMMA Portal extract. Your Implementation manager will walk you through the file to help you interpret and use the data.