Adapter

1. Method : GET /adapter

Expected : Displays the data json adapter that the user has.
Actual : According to expectations.

2. Method : GET /adapter/all

Expected : Displays the json data adapter provided by ask-fast.
Actual : According to expectations.

3. Method : POST /adapter/buy/phonenumbers

4. Method : GET /adapter/configsraw

5. Method : GET /adapter/isFree

Expected : The API will display the status of the adapter whether the adapter
status is free or not.
Actual : According to expectations.

6. Method : GET /adapter/property/{adapterId}

7. Method : DELETE /adapter/release/{adapterId}

8. Method : GET /adapter/search

Expected : The API will display data adapters according to the type of adapter.
Actual : According to expectations.

9. Method : DELETE /adapter/{adapterId}

Expected : Remove adapters from users according to adapterId.
Actual : The data adapter was successfully deleted from the list of adapter
users, but in the response body there was no information indicating
that the process of removing the adapter was successful.

10.Method : GET /adapter/{adapterId}

Expected : The API will display data adapters according to the adapterId.
Actual : According to expectations.
Address
1. Method : GET /address
Expected : Display the user's address.
Actual : Display empty data user’s address. According to expectations.

2. Method : POST /address

3. Method : DELETE /adapter/{addressId}

4. Method : GET /adapter/{postCode}/{houseNumber}

Note :
When I do the test I am confused about the address, where is this address from the
Dialog for adapters or indeed the user's address. But when I see the API for retrieving
address data through postal codes and house numbers, I think the address here is the
user's address. But the problem is that in the profile users section there is no function
that adds the user's address and displays it on the web. So the API cannot be tested in
its entirety.

Dialog
1. Method : GET /dialog
Expected : Display the data dialog that the user has.
Actual : According to expectations.

2. Method : POST /dialog

Expected : Create a new dialog according to the parameters requested.
Actual : The dialog was successfully created.

3. Method : DELETE /dialog/all

Expected : Delete all dialog from user’s.
Actual : All dialog was successfully deleted. But no content in response body.

4. Method : GET /dialog/getByName

Expected : Display the data dialog according to the name of the dialog.
Actual : According to expectations.

5. Method : DELETE /dialog/{uuid}

Expected : Delete the data dialog in accordance with the dialogId.
Actual : Dialog was successfully deleted. But no content in response body.

6. Method : GET /dialog/{uuid}

Expected : Get the data dialog in accordance with the dialogId.
Actual : Display dialog data in accordance with dialogId.
 7. Method : PUT /dialog/{uuid}
Expected : Change data dialog according to dialogId.
Actual : Data changes according to changes made by user’s.

8. Method : GET /dialog/{uuid}/adapters

Expected : Display the data adapter that is connected to the dialog in
accordance with the ID dialog.
Actual : According to expectations.

HttpLog
1. Method : GET /httplog/{ddrRecordId}
Expected : Display the data log according to the id of the dialog.
Actual : According to expectations.

Info
1. Method : GET /info
Expected : Display the Account information.
Actual : According to expectations.

2. Method : DELETE /info/availability/{source}

3. Method : GET /info/availability/{source}

Expected : Display the availability account according source.
Actual : Give the response Body is “null”.

4. Method : PUT /info/availability/{source}

5. Method : PUT /info/blacklistedaddress/unsubscribe/{adapterNumber}

6. Method : GET /info/blacklistedaddress/{blockedAddress}

Expected : Display the availability account according source.
Actual : Give the response Body with result is “null”.

7. Method : DELETE /info/blacklistedaddress/{blockedAddress}

8. Method : PUT /info/blacklistedaddress

9. Method : PUT /info/blacklistedaddress

Note :
I am very difficult to test API on Info because of the lack of explanation, especially
when the method used is PUT and Delete, where there are no examples of bodies
given. This also relates to the availability of the user where the tests performed must
use the Ask-fast Company application because the website does not support the
function.