-
Notifications
You must be signed in to change notification settings - Fork 9
Consumer App
Ankit Bhanvadia edited this page Oct 24, 2016
·
11 revisions
Consumer app allows a user to register their application with OAuth server to access OAuth server API. It a similar concept as Facebook App creation to access Facebook API.
A consumer app can only be created by a user if they have admin role in OAuth system. It has many-to-one relation with the service. i.e, A user can create many apps for a single service. It will be distinguished by ClientId and Secret. A user can create a new app with following details.
- Name : Name of the application (It needs to be unique)
- Description : Description about application (Required)
- Callback Url: Callback URL after user has been authenticated (Required and Valid URL)
The administrator can update any app and change any of the properties except Name. A user can regenerate ClientId and Secret if required.
S.No | Title | Action | Expected Result |
---|---|---|---|
(A) | Add Consumer App | ||
1) To verify Add a New App | It should able to click on add a new app button. | ||
2) To verify enter the Name | It should allow entering the name in the given field. | ||
3) To verify whether the name is reached the maximum length or not | It should allow only 255 characters in the name not more than that. | ||
4) To verify the Name is not written | It should show an error message as "Name is Required". | ||
5) To verify enter the Description | It should allow entering the description in the given field. | ||
6) To verify whether the description is reached the maximum length or not | It should allow only 1000 characters in the description not more than that. | ||
7) To verify the Description is not written | It should show an error message as "Description is Required". | ||
8) To verify enter the Call Back URL | It should allow entering the call back URL in the given field. | ||
9) To verify whether the call back URL is reached the maximum length or not | It should allow only 255 characters in the call back URL not more than that. | ||
10) To verify whether Call Back URL is valid or invalid | It should allow entering the valid URL as Domain name followed by API | ||
11) To verify Call Back URL is not written | It should show an error message as "Call Back URL is Required". | ||
12) To verify click on Submit Button | It should allow clicking on submit button. | ||
13) To verify whether the message is been displayed or not | It should display a message as "Consumer App is added Successfully". | ||
14) To verify if all the fields are blank | It should not allow the user to click on Submit button. | ||
(B) | Edit Consumer App | ||
1) To verify Edit Consumer App click on the added consumer app | It should allow the user to click on added project for edit. | ||
2) To verify user can edit the various details Name, Description and Call Back URL | It should allow the user to edit various fields such as Name, Description and Call Back URL. | ||
3) To verify whether the update information is updated or not | It should allow the user to click on update button and user can see the updated information. | ||
4) To verify whether the message is been displayed or not | It should allow the user to see a message when we click on update button. |
Add mockups in PNG format
Add final design here