You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API GET: /api/services/servicerelease/{serviceId}/technical-user-profiles need to be enhanced to deliver the parameter "type": "internal" | "external" count: number parameter should be implemented to provide the amount of technical user accounts that will be provided.
Acceptance Criteria
API provides the typeof technical user account
the API provides the number of technical user accounts
Test Cases
Test Case 1: Verify the type parameter for technical user accounts Description: Validate that the API GET: /api/services/servicerelease/{serviceId}/technical-user-profiles returns the type parameter with the value internal or external for each technical user account. Steps:
Send a GET request to the API endpoint GET: /api/services/servicerelease/{serviceId}/technical-user-profiles.
Verify that the response contains the type parameter for each technical user account.
Ensure that the type parameter has a value of either internal or external. Expected Result: The API response should include the type parameter for each technical user account, and the value should be either internal or external.
Test Case 2: Verify the count parameter for technical user accounts Description: Validate that the API GET: /api/services/servicerelease/{serviceId}/technical-user-profiles returns the count parameter with the number of technical user accounts provided.
Steps:
Send a GET request to the API endpoint GET: /api/services/servicerelease/{serviceId}/technical-user-profiles.
Verify that the response contains the count parameter.
Ensure that the count parameter value matches the number of technical user accounts returned in the response. Expected Result: The API response should include the count parameter, and the value should match the number of technical user accounts provided in the response.
The text was updated successfully, but these errors were encountered:
Description
The API
GET: /api/services/servicerelease/{serviceId}/technical-user-profiles
need to be enhanced to deliver the parameter"type": "internal" | "external"
count: number
parameter should be implemented to provide the amount of technical user accounts that will be provided.Acceptance Criteria
type
of technical user accountTest Cases
Test Case 1: Verify the type parameter for technical user accounts
Description: Validate that the API GET: /api/services/servicerelease/{serviceId}/technical-user-profiles returns the type parameter with the value internal or external for each technical user account.
Steps:
Send a GET request to the API endpoint GET: /api/services/servicerelease/{serviceId}/technical-user-profiles.
Verify that the response contains the type parameter for each technical user account.
Ensure that the type parameter has a value of either internal or external.
Expected Result: The API response should include the type parameter for each technical user account, and the value should be either internal or external.
Test Case 2: Verify the count parameter for technical user accounts
Description: Validate that the API GET: /api/services/servicerelease/{serviceId}/technical-user-profiles returns the count parameter with the number of technical user accounts provided.
Steps:
Send a GET request to the API endpoint GET: /api/services/servicerelease/{serviceId}/technical-user-profiles.
Verify that the response contains the count parameter.
Ensure that the count parameter value matches the number of technical user accounts returned in the response.
Expected Result: The API response should include the count parameter, and the value should match the number of technical user accounts provided in the response.
The text was updated successfully, but these errors were encountered: