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, this list 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.
| Test Case | API Endpoint | Suggested Test Case | Expected Result |
|---|---|---|---|
| 1 | Address Search | Retrieve matching addresses by supplying a search term where the request returns matches. |
Using auto-complete logic, if the pageSize query parameter is not specified then the results json array, of up to 5 address matches, will be returned otherwise will be limited up to the specified valid pageSize value.
Each record in the results array will contain:
The pagination links will be provided (HATEOAS). The HTTP status code will be a 200 (OK). |
| 2 | Address Search | Retrieve matching addresses by supplying a search term where the request does not return matches. |
An empty results array will be returned. The HTTP status code will be a 200 (OK). |
| 3 | Address Search | Retrieve matching addresses using a query parameter that is invalid (e.g. pageSize greater than 20). |
An HTTP status code other than 200 is returned. Please refer to Error Codes for the specific error response payload. |
| 4 | Address Details | Retrieve address details by supplying a valid Fibre Service Location Identifier (FSL ID). |
Address details are returned. 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. |
| 5 | Address Details | Retrieve address details by supplying a valid TUI identifier (TUI ID). |
Address details are returned. 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. |
| 6 | Address Details | Retrieve address details by supplying an invalid address identifier. |
An HTTP status code other than 200 or 203 is returned. Please refer to Error Codes for the specific error response payload. |
Test Data
The table below shows a list of query parameters provided for the Test Cases.
Address Search Test Data
| Test Case | Search Term (q) | Page | Page Size |
|---|---|---|---|
| 1 | 106 Wrights Road | 1 | 5 |
| 1 | 106 Wrights Road | 2 | 1 |
| 2 | 00 Wrights Road | 1 | 5 |
| 3 | 106 Wrights Road | 1 | 5 |
Address Details Test Data
| Test Case | FSL ID | TUI ID |
|---|---|---|
| 4 | 30003729CESLCF7 | - |
| 4 | 30191951CESLCE1 | - |
| 4 | 30210058CESL894 | - |
| 4 | 30210059CESLC16 | - |
| 5 | - | 1002821287 |
| 5 | - | 1002821288 |
| 6 | FSL001 | - |
| 6 | - | 0 |
| 6 | - | 1 |
| 6 | - | TUI001 |