-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
4414b90
commit ec4a41d
Showing
16 changed files
with
126 additions
and
16 deletions.
There are no files selected for viewing
2 changes: 1 addition & 1 deletion
2
...os/core/functional/api/endpoints/apiaccess/delete-api-api-client-apiclientid.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
29 changes: 29 additions & 0 deletions
29
...ontent/scenarios/core/functional/api/endpoints/apiaccess/post-api-api-client.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
--- | ||
title: "POST /api/api-client" | ||
weight: 1 | ||
--- | ||
|
||
# POST /api/api-client | ||
## Details | ||
* **Component** : Core | ||
* **Status** : [TEST] Automation in progress | ||
* **Automated on** : 9.0.x | ||
* **Scenario** : https://forge.prestashop.com/browse/TEST-8629 | ||
|
||
## Steps | ||
| Step Description | Expected result | | ||
| ----- | ----- | | ||
| In BO, Go to Advanced Parameters > Authorization Server | Authorization Server Page is displayed correctly.<br>No records found in the table | | ||
| Click on the button "Add new API access" | New API access Page is displayed correctly | | ||
| Fill the form with following data (Client ID : "Client XYZ", Client Name: "ClientName ABC")<br>Click on "Generate client secret & Save" button | There is 1 application in the list<br>The message “The API access and Client secret has been generated sucessfully” is displayed<br>The message "Client secret: " is available<br>The button Copy put the client secret in the clipboard | | ||
| Request with method POST the endpoint "https://[url of your shop]/admin-dev/index.php/api/api-client/\{apiClientId}" with data | The HTTP code is 201.<br><br>The response is in JSON. | | ||
| In BO, Go to Advanced Parameters > Authorization Server | Authorization Server Page is displayed correctly.<br>Two records found in the table.<br>Check fields like apiClientId, clientId, clientName. | | ||
| Go to edit page | Edit API access Page is displayed correctly<br>Check fields like description, enabled, lifetime, scopes | | ||
| Go to Advanced Parameters > Authorization Server | Authorization Server Page is displayed correctly. | | ||
| On the second row, click on the button “Three points” | The dropdown is displayed. | | ||
| Click on the Delete Button in the dropdown | A modal appeared | | ||
| Click on the Confirm Button in the modal | The message “Successful deletion” is displayed<br>One record found in the table | | ||
| In BO, Go to Advanced Parameters > Authorization Server | Authorization Server Page is displayed correctly.<br>1 record found in the table | | ||
| On the first row, click on the button “Three points” | The dropdown is displayed | | ||
| Click on the Delete Button in the dropdown | A modal appeared | | ||
| Click on the Confirm Button in the modal | The message “Successful deletion” is displayed<br>No records found in the table | |
36 changes: 36 additions & 0 deletions
36
...nctional/api/endpoints/customergroup/put-api-customers-group-customergroupid.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
--- | ||
title: "PUT /api/customers/group/{customerGroupId}" | ||
weight: 2 | ||
--- | ||
|
||
# PUT /api/customers/group/{customerGroupId} | ||
## Details | ||
* **Component** : Core | ||
* **Status** : [TEST] Automation in progress | ||
* **Automated on** : 9.0.x | ||
* **Scenario** : https://forge.prestashop.com/browse/TEST-8628 | ||
|
||
## Steps | ||
| Step Description | Expected result | | ||
| ----- | ----- | | ||
| In BO, Go to Advanced Parameters > Authorization Server | Authorization Server Page is displayed correctly.<br>No records found in the table | | ||
| Click on the button "Add new API access" | New API access Page is displayed correctly | | ||
| * Fill the form with following data<br> * Click on "Generate client secret & Save" button | * The message “The API access and Client secret has been generated sucessfully” is displayed<br> * The message "Client secret: " is displayed | | ||
| Return to BO > Advanced Parameters > Authorization Server and get the ID of the first row | Authorization Server Page is displayed correctly.<br>1 record found in the table | | ||
| In BO, Go to Shop Parameters > Customer Settings | Customer Settings Page is displayed correctly. | | ||
| Click on the Groups tab | Customers - Groups page is well displayed | | ||
| Reset all filters of Groups table | All filters are reset. All Groups are displayed | | ||
| Click “Add new group” | The “Add new” page should be displayed correctly | | ||
| Create a new Customer group > Save | Message “Successful creation” is displayed<br><br>There is one more group in the list. | | ||
| Filter by groupe name with the name of the created group | 1 record found | | ||
| Request with method PUT the endpoint "https://[url of your shop]/admin-dev/index.php/api/customers/group/\{customerGroupId}" with modified data (relative to the data used for the creation) | The HTTP code is 200.<br><br>The return value is in JSON<br><br>The return value data are consistent relative to sent data. | | ||
| Filter by groupe ID with the ID of the created group | 1 record found | | ||
| Click on Edit for the filtered group | The Edit page will be displayed correctly<br><br>The return data keys are consistent relative to BackOffice data. | | ||
| Click on the Groups tab | Customers - Groups page is well displayed | | ||
| Filter by groupe ID with the ID of the created group | 1 record found | | ||
| Delete the filtered group > Click Yes | Message “Successful deletion” is displayed<br><br>The filtered group is deleted | | ||
| Reset all filters of Groups table | All filters are reset. All Groups are displayed | | ||
| In BO, Go to Advanced Parameters > Authorization Server | Authorization Server Page is displayed correctly.<br>1 record found in the table | | ||
| On the first row, click on the button “Three points” | The dropdown is displayed | | ||
| Click on the Delete Button in the dropdown | A modal appeared | | ||
| Click on the Confirm Button in the modal | The message “Successful deletion” is displayed<br>No records found in the table | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters