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
Add additional mandatory field "DUMP REASON" when enabling the dump level for customer auth
IN CUSTOMERS AUTHS TABLE: Add Column name: DUMP REASON
Acceptance criteria: I can see DUMP REASON COLUMN inside table of /customers_auths is added after DUMP LEVEL
CUSTOMERS AUTHS ID EDIT: Add additional mandatory field "DUMP REASON" only when "DUMP LEVEL" is enabled (changed from capture nothing to any)
Acceptance criteria:
I can see "DUMP REASON" in /customers_auths/{id}
I can see DUMP REASON in /customers_auths/{id}/edit
I must enter DUMP REASON when Dump level is ENABLED(changed from capture nothing to ANY other)
Scenarios: Given I want to enable Dump level for customer auth When I Edit Customer Auth /customers_auths/{id}/edit And Select DUMP LEVEL = 1. Capture signalling traffic OR 2. Capture rtp traffic OR 3. Capture all traffic Then I must enter "DUMP REASON" any plain text And If do not enter DUMP Reason I can see error or verification "Dump reason can't be blank"
Given I want to DISABLE Dump level for customer auth When I Edit Customer Auth /customers_auths/{id}/edit And Select DUMP LEVEL = 1. Capture nothing Then I can see "DUMP REASON" is not mandatory and can be left EMPTY
REASON:
When debug is ENABLED it is using server resources.
Dump Reason would help to review customer auths with dump enabled and manage them accordingly.
Also you can see a reason why it was enabled.
Thanks
The text was updated successfully, but these errors were encountered:
Add additional mandatory field "DUMP REASON" when enabling the dump level for customer auth
Add Column name: DUMP REASON
Acceptance criteria: I can see DUMP REASON COLUMN inside table of /customers_auths is added after DUMP LEVEL
Add additional mandatory field "DUMP REASON" only when "DUMP LEVEL" is enabled (changed from capture nothing to any)
Acceptance criteria:
Scenarios:
Given I want to enable Dump level for customer auth
When I Edit Customer Auth /customers_auths/{id}/edit
And Select DUMP LEVEL = 1. Capture signalling traffic OR 2. Capture rtp traffic OR 3. Capture all traffic
Then I must enter "DUMP REASON" any plain text
And If do not enter DUMP Reason I can see error or verification "Dump reason can't be blank"
Given I want to DISABLE Dump level for customer auth
When I Edit Customer Auth /customers_auths/{id}/edit
And Select DUMP LEVEL = 1. Capture nothing
Then I can see "DUMP REASON" is not mandatory and can be left EMPTY
REASON:
When debug is ENABLED it is using server resources.
Dump Reason would help to review customer auths with dump enabled and manage them accordingly.
Also you can see a reason why it was enabled.
Thanks
The text was updated successfully, but these errors were encountered: