Enable is committed to supporting your development and testing, ensuring integration is simple and robust.
As with any software development, Enable encourages you to test your application with both positive and negative scenarios.
A list of example test cases has been provided for your convenience; however, is not intended to be comprehensive and some test cases may not apply to your use of the API.
Please ensure your test cases are relevant to your business and specific use cases.
Test Cases
The table below provides details of suggested test cases.
| Suggested Test Case | Expected Result |
|---|---|
| Get fibre service details where a valid Enable Fibre Service Identifier (Service ID) is provided |
Fibre service details are returned, along with enriched ONT information. The HTTP status code may be a 200 (OK) or a 203. A 203 status code would be returned if the response has been cached by the API for faster response times. |
| Create an ONT Status test for a fibre service where a valid Enable Fibre Service Identifier (Service ID) is provided | Test ID is returned. The HTTP status code will be a 201 (Created). |
| Get an ONT Status test result for a valid test identifier (test ID) | ONT Status test result is returned. The HTTP status code will be a 200 (OK). |
| Get an ONT Status test result for an invalid test identifier (test ID) | Error response is returned. Please refer to Error Codes for the specific error response payload. |
| Get all fibre test results for a valid Enable Fibre Service Identifier (Service ID) | All fibre test results for the Service ID are returned. The HTTP status code will be a 200 (OK). |
| Get all fibre test results for a valid Enable fibre service identifier (Service ID) that has no ONT Status test results | An empty data array will be returned. The HTTP status code will be a 200 (OK). |
Test Data
The table below provides a list of Service IDs configured in the sandbox environment to return a simulated response for each endpoint.
The Service IDs will return valid response payloads for a GET Product request, assuming the request is correctly formatted. These are stubbed sample responses and the details in the response will match the details shown in the table.
These Service IDs can be used with POST Tests to create an ONT Status Test. A Test ID will be returned. Use the Test ID with Get Test to obtain a test response. The test response will always contain the Service ID of the service the test is associated with for cross-referencing purposes.
The Service ID, used with a GET Tests request, will return all ONT Status Test results for the provided service.
Fibre Sample Responses with Valid Payloads
| Service ID | Product Family | Product Name | Bundled ATA Present | ONT Status | ONT Model | ONT Mode | Tagging Mode |
|---|---|---|---|---|---|---|---|
| ENENAB02306049 | Bitstream 2a | BS2a 100/20 CIR 2.5/2.5 | No | good | HG8240H | Standard | Untagged |
| ENENAB02306052 | ATA | Baseband Voice | Yes | good | HG8240 | Standard | Tagged |
| ENENAB02306047 | Bitstream 2a | BS2a 30/10 CIR 2.5/2.5 | Yes | good | HG8240H | Standard | Tagged |
| ENENAATA306047 | ATA | Bundled ATA Port | Yes | good | HG8240H | Standard | Tagged |
| ENENAB02306183 | Bitstream 2a | BS2a 200/100 CIR 2.5/2.5 | Yes | switched_off | HG8240H | Standard | Unknown |
| ENENAATA306183 | ATA | Bundled ATA Port | Yes | switched_off | HG8240H | Standard | Unknown |