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
We need an additional name field to allow users to enter a "preferred name" so that people who do not use their full legal name to identify themselves can do so when registering.
single name field may contain spaces and multiple words
150 char (Avinash will check what BCROS standard is) (Confirmed with Ethan Pitt, see comments below)
UTF8
optional
Acceptance Criteria
Feature: Preferred Name Form Component
Scenario: Entering a single word in the Preferred Name field
Given the user is on the form with the Preferred Name field
When the user enters a single word into the Preferred Name field
Then the input should be successfully validated
Scenario: Entering multiple words separated by spaces in the Preferred Name field
Given the user is on the form with the Preferred Name field
When the user enters "John Doe" into the Preferred Name field
Then the input should be successfully validated
Scenario: Leaving the Preferred Name field blank
Given the user is on the form with the Preferred Name field
When the user leaves the Preferred Name field blank
Then the input should be successfully validated since the field is optional
Scenario: Entering a name that exceeds the character limit
Given the user is on the form with the Preferred Name field
When the user enters a name that is 251 characters long
Then the user should receive a validation error stating the 250 character limit
Scenario: Entering a name with special characters using UTF8 encoding
Given the user is on the form with the Preferred Name field
When the user enters a name containing UTF8 special characters
Then the input should be successfully validated
The text was updated successfully, but these errors were encountered:
We need an additional name field to allow users to enter a "preferred name" so that people who do not use their full legal name to identify themselves can do so when registering.
Design Ticket
UI Design: Preferred Name #18168
Instructions
Place under legal name
make it optional
single name field may contain spaces and multiple words
150 char (Avinash will check what BCROS standard is) (Confirmed with Ethan Pitt, see comments below)
UTF8
optional
Acceptance Criteria
Feature: Preferred Name Form Component
Scenario: Entering a single word in the Preferred Name field
Given the user is on the form with the Preferred Name field
When the user enters a single word into the Preferred Name field
Then the input should be successfully validated
Scenario: Entering multiple words separated by spaces in the Preferred Name field
Given the user is on the form with the Preferred Name field
When the user enters "John Doe" into the Preferred Name field
Then the input should be successfully validated
Scenario: Leaving the Preferred Name field blank
Given the user is on the form with the Preferred Name field
When the user leaves the Preferred Name field blank
Then the input should be successfully validated since the field is optional
Scenario: Entering a name that exceeds the character limit
Given the user is on the form with the Preferred Name field
When the user enters a name that is 251 characters long
Then the user should receive a validation error stating the 250 character limit
Scenario: Entering a name with special characters using UTF8 encoding
Given the user is on the form with the Preferred Name field
When the user enters a name containing UTF8 special characters
Then the input should be successfully validated
The text was updated successfully, but these errors were encountered: