Purpose
This page lists out the test activities to be carried out against the different form elements and components. It is to be used as a checklist for testing. All test scenarios listed for each form element might not apply to the area under test but should act as a guideline to spur thinking as the test activity is conducted.
The form elements in scope are listed on the UX terms page
Form Elements
The test scenarios below apply to all form elements and is not explicitly called out against each form element
- User friendliness
- Browser compatibility
- Responsive on mobile applications
Titles
| Title Type | Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|---|
| Service Title | 1. Exact spelling as per catalog 2. Exact casing as per catalog (title case vs sentence case) 3. Title if long wraps (if applicable) 4. Look/positioning similar to UX design system (or as specified in the catalog) It is a Level 1 title (h1) (unless catalog says otherwise) | And I expect service-title <SERVICE TITLE> Example: And I expect service-title Register a natural person |
| Entity Title | 1. Exact spelling as per catalog 2. Exact casing as per catalog (title case vs sentence case) 3. Title if long wraps (if applicable) 4. Look/positioning similar to UX design system (or as specified in the catalog) It is a Level 2 title (h2) (unless catalog says otherwise) | And I expect entity-title <ENTITY TITLE> Example: And I expect entity-title John Smith |
| Entity Type Title | 1. Exact spelling as per catalog 2. Exact casing as per catalog (title case vs sentence case) 3.Title if long wraps (if applicable) 4. Look/positioning similar to UX design system (or as specified in the catalog) It is plain text size (unless catalog says otherwise) | And I expect entity-type-title <ENTITY TYPE TITLE> Example: And I expect entity-type-title Persons |
| Group Title | 1. Exact spelling as per catalog 2. Exact casing as per catalog (title case vs sentence case) 3. Title if long wraps (if applicable) 4. Look/positioning similar to UX design system (or as specified in the catalog) Level 3 title (unless catalog says otherwise) | And I expect group-title <GROUP TITLE> Example: And I expect group-title Other details |
| Section title | 1. Exact spelling as per catalog 2. Exact casing as per catalog (title case vs sentence case) 3. Title if long wraps (if applicable) 4. Look/positioning similar to UX design system (or as specified in the catalog) Level 2 title, regular (unless catalog says otherwise) | And I expect section-title <SECTION TITLE> Example: Then I expect section-title Personal details |
| Accordion Section Title | 1. Exact spelling as per catalog 2. Exact casing as per catalog (title case vs sentence case) 3. Title if long wraps (if applicable) 4. Look/positioning similar to UX design system (or as specified in the catalog) Level 2 title, regular (unless catalog says otherwise) | And I expect accordion-section-title <ACCORDION SECTION TITLE> Example: And I expect accordion-section-title Main place of business |
| Label | 1. Exact spelling as per catalog 2. Exact casing as per catalog (title case vs sentence case) 3. Title if long wraps (if applicable) 4. Look/positioning similar to UX design system (or as specified in the catalog) Plain text size (unless catalog says otherwise) | And I expect text <LABEL> Example: And I expect text Full name |
| Help-title | 1. Exact spelling as per catalog 2. Exact casing as per catalog (title case vs sentence case) 3. Title if long wraps 4. Clicking help-title displays help-text. Clicking it again collapses it. 5. Look/positioning similar to UX design system (or as specified in the catalog) | Activity: Validate help title And I expect help-title <HELP TITLE> Example: And I expect help-title Are your applicant details incorrect? Activity: Click to expand help title. Click again to collapse it. TODO: |
| Help – text | 1.Exact spelling as per catalog 2. Exact casing as per catalog (title case vs sentence case) 3. Look/positioning similar to UX design system (or as specified in the catalog) | And I expect help-text <HELP TEXT> Example: And I expect help-text You must be at least 18 years old to register as a professional |
| Hint | 1. Exact spelling as per catalog 2. Exact casing as per catalog (title case vs sentence case) 3. Look/positioning similar to UX design system (or as specified in the catalog) | And I expect hint <HINT> Example: And I expect hint This is a hint text |
| Step Title | 1. Exact spelling as per catalog 2. Exact casing as per catalog (title case vs sentence case) 3. Look/positioning similar to UX design system (or as specified in the catalog) | I click step-title <STEP TITLE NAME> Example: And I click step-title General Details Note: You can only click steps that are active. If the step is not active you cannot click them. Active steps can be determined by the step having a link as per screenshot below  |
Text Box
| Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|
| 1. Valid characters 2. Invalid characters 3. Special characters http://www.columbia.edu/~fdc/utf8/ᛋᚳᛖᚪᛚ᛫ᚦᛖᚪᚻ᛫ᛗᚪᚾᚾᚪ᛫ᚷᛖᚻᚹᛦᛚᚳ᛫ᛗᛁᚳᛚᚢᚾ᛫ᚻᛦᛏ᛫ᛞᚫᛚᚪᚾSîne klâwen durh die wolken sint geslagen 4. End of line characters 5. Spaces – Leading spaces, Trailing spaces, only spaces (single space, multiple spaces) 6. Text field with numbers -integers, decimals, formatted numbers, boundary conditions(0 , 32768, 32769, 65536, 65537, 2147483648, 2147483649), scientific notation (1E-16), with commas (1,234,567) 7. Field length limitations Copy paste a string that exceeds limitations – does it truncate 8. Mandatory field 9. Default values (loaded from a previous transaction) 10. Action Copy paste allowed 11. Selection using mouse or TAB keyboard key selection 12. Look/positioning similar to UX design system (or as specified in the catalog) 13. Copy pasting html tags, javascript code | Enter Text into an editable text box And I enter text <TEXT> in <LABEL OF TEXT BOX> Note: If text is already present will not clear but will append to existing text in the text box Example: And I enter text Tasmania in City Clear Text in editable text box And I clear text in <LABEL OF TEXT BOX> Example: And I clear text in CitySet Text Set Text in editable text box And I set text <TEXT> in <LABEL OF TEXT BOX> Note: Clears the text and then enters the text in an editable text box. If you have to do a lot of clearing text and entering text best to use “Set Text” Example: And I set text Tasmania in CityExpect Expect Value – This only applies to prepopulated editable text boxes And I expect <LABEL OF TEXT BOX> to have value <VALUE> Example: And I expect Mobile number > Number to have value 123456789 Expect no value – This applies to scenarios where we are prepopulating certain fields on the form and other fields should be empty And I expect <LABEL OF TEXT BOX> to have no value Example: And I expect Mobile number > Number to have no value Text box cannot be edited (read-only) And I expect <LABEL OF TEXT BOX> to be read-only Example: And I expect City to be read-only Text box should not be present on the screen And I do not expect textbox <LABEL OF TEXT BOX> Example: And I do not expect textbox City Maximum length when exceeded triggers the right alert message Note: This step will not work if a mask of maximum limit has been configured in the field Numeric field And I validate <LABEL OF TEXT BOX> has max-length of <MAX-LENGTH AS PER CATALOG> digits with <TYPE OF ALERT MESSAGE> <MESSAGE TEXT> Example: And I validate Mobile number has max-length of 10 digits with error message Mobile number cannot be more than 10 digits Alphabetic field And I validate <LABEL OF TEXT BOX> has max-length of <MAX-LENGTH AS PER CATALOG> letters with <TYPE OF ALERT MESSAGE> <MESSAGE TEXT> Example: And I validate Given name has max-length of 20 letters with warning message Given name cannot be more than 20 letters Alphanumeric field And I validate <LABEL OF TEXT BOX> has max-length of <MAX-LENGTH AS PER CATALOG> characters with <TYPE OF ALERT MESSAGE> <MESSAGE TEXT> Example: And I validate Street address has max-length of 100 characters with info message Street address cannot be more than 100 characters |
Body Text
| Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|
| 1. Exact spelling as per catalog 2. Exact casing as per catalog (title case vs sentence case) 3. Text if long wraps correctly 4. Look/positioning similar to UX design system (or as specified in the catalog) | Expect Text Used for 1.Validating contents of read only fields on a form 2.Validating error messages on a form And I expect text <TEXT> Example: And I expect text Please enter a date And I expect text No results found for current criteria. Please change criteria and try again. Do not expect text And I do not expect text <TEXT> Example: And I do not expect text Submitted date Check format – where data is dynamic TODO: – regular expressions |
Date field
| Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|
| 1. Time zones 2. Leap Days 3. Always invalid days (Feb 30, Sept 31) 4. Feb 29 in Non-Leap Years 5. Time format (ATPAT-346) 6. Date Constraints (minimum date allowed, maximum date allowed) 7. Look/positioning similar to UX design system (or as specified in the catalog) | Enter Date in an editable Date Field And I enter date <DATE> in <LABEL OF DATE FIELD> Example: And I enter date 1-November-2019 in End date1-November-2019 And I enter date #FORMATTED_TODAY#dd-MMMM-YYYY#FORMATTED_TODAY# in Status change date Note: If date is a single digit use single digit (ex: 1 instead of 01) Clear Date in an editable Date Field And I clear date in <LABEL OF DATE FIELD> Example: And I clear date in End date Set Date in an editable Date Field – Clears the date and then enters the date And I set date <DATE> in <LABEL OF DATE FIELD> Example: And I set date #FORMATTED_TODAY#dd-MMMM-YYYY#FORMATTED_TODAY# in Status change date Expect Date in an editable Date Field – date prepopulated in the date field Example: And I expect <LABEL OF DATE FIELD> to have date #FORMATTED_TODAY#dd-MMMM-YYYY#FORMATTED_TODAY# And I expect Date of birth to have date #FORMATTED_TODAY#dd-MMMM-YYYY#FORMATTED_TODAY# And I expect Date of birth to have date 3-April-2000 Expect no prepopulated date in an editable Date Field And I expect <LABEL OF DATE FIELD> to have no date Example: And I expect Date of birth to have no date Entering invalid dates And I enter 30-Feb-1982 in Status change date And I enter 29-Feb-2019 in Status change date And I enter 31-Jun-1988 in Status change date Some useful Date formats for Hercules Tests (change label of date field as required) Enter today’s date And I enter date #FORMATTED_TODAY#dd-MMMM-YYYY#FORMATTED_TODAY# in Status change date Entering a date in the past Example 1:And I enter date #DATEONLY_FORMATTED: 1 month ago FORMAT:dd-MMMM-yyyy# in Status change date Example 2: Using a variable (if we need to use it or access it later on) And I create a variable called pastDate with value #DATEONLY_FORMATTED: 17 years ago FORMAT:dd-MMMM-yyyy# And I enter date ${pastDate} in Date of birth Other examples are: 2 years ago, 1 month ago, three weeks ago, last wednesday, 3 days ago, yesterday, today Entering a date in the future Example 1: And I enter date #DATEONLY_FORMATTED: 2 years from now FORMAT:dd-MMMM-yyyy# in Status change date Example 2: Using a variable (if we need to use it or access it later on) And I create a variable called futureDate with value #DATEONLY_FORMATTED: 2 years from now FORMAT:dd-MMMM-yyyy# And I enter date ${futureDate} in Status change date Other examples are: tomorrow, 3 days from now, next thursday, next week, three weeks from now, 1 month from now,1 year from now, 2 years from now, next month, next year |
Button
| Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|
| 1. Button style as per requirements 2. Button functions Submit 1. Mandatory fields not filled in show up with error messages 2.Changes are applied 3.Takes you to the next relevant page (ex – Confirmation screen) Cancel 1.If cancelling out get a confirmation popup as applicable 2.Changes are not applied 3.Takes you to the next relevant page (ex. Dashboard) Continue 1.Changes are not applied. 2.Takes you to the next relevant page (ex – Review and Submit) 3. Selection using mouse or TAB keyboard key selection 4.Look/positioning similar to UX design system (or as specified in the catalog) | Click button I click button <BUTTON LABEL> Example: And I click button Search Validate button text Note: Only use this if you are not clicking on the button. Click button automatically validates the button text I expect text <BUTTON TEXT> And I expect text Add an Additional Business Location Button should not be present on the screen I do not expect button <BUTTON LABEL> And I do not expect button Search Type of button TODO: – primary/secondary/rounded, etc |
Radio Button
| Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|
| 1. Radio button alignment (Horizontal/Vertical) 2. All required options listed 3. Mandatory field 4. Default option selected (if applicable) 5. Check if the radio button allows one selection or more than one selection a. If single selection are we able to select more than one (negative test case) b. If multiple options can be selected, can it be done and values populating correctly in the database 6. Radio button selection using mouse cursor action or TAB keyboard key selection 7. Test with all possible options and ensure that the form/database is updated with the choice being made 8. Check if the radio button alignment on the form page is proper or not 9. Check if the label and options for the radio button is properly aligned. 10. Look/positioning similar to UX design system (or as specified in the catalog) | Select radio button And I select radio button <OPTION NAME> in radio button group <RADIO BUTTON LABEL> Example: And I select radio button Cancelled in radio button group Status Radio button should not be present on the screen I do not expect radio-button-group <RADIO BUTTON LABEL>(Note: the hyphen in radio-button-group) Example: And I do not expect radio-button-group Status Radio button is read-only and value cannot be changed I expect radio button <OPTION NAME> in radio button group <RADIO BUTTON LABEL> to be read-only(Note: the hyphen between read and only) Example: And I expect radio button Cancelled in radio button group Status to be read-only Option selected – (Prepopulated/Default value) I expect radio button <OPTION NAME> in radio button group <RADIO BUTTON LABEL> to have option selected Example: And I expect radio button Male in radio button group Gender to have option selected No option selected I expect radio button group <RADIO BUTTON LABEL> to have no option selected Example: And I expect radio button group Gender to have no option selected |
Drop Down (Select Option field)
Note: This also works for autocomplete fields
| Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|
| 1. All required options listed 2. All required options listed in the right order 3. Mandatory field 4. Font for options matches the form requirements 5. Drop Down selection using mouse cursor action or TAB keyboard key selection 6. Drop Down value selection using arrow key 7. Value selection is reflected correctly on the form and also in the database when value saved 8. Check if the dropdown alignment on the form page is proper or not. 9. Check if the label for the dropdown is properly aligned. 10. Look/positioning similar to UX design system (or as specified in the catalog) | Select value in a dropdown I select option <OPTION NAME> from dropdown <DROPDOWN LABEL> Example: And I select option Male from dropdown Gender Check presence of value in a dropdown Note: (If populated from a list of values ensure that all the values exist as per catalog) Order cannot be validated via automation. Only the presence of values can be checked. Also this step shall not select the value in the dropdown. I expect dropdown <DROPDOWN LABEL> to have option<VALUE> Example: And I expect dropdown Select Name to have option Marcus Arora Check selected value in a dropdown – Preppopulated field/Default value I expect dropdown <DROPDOWN LABEL> to have selection <DEFAULT SELECTION> Example: And I expect dropdown Gender to have selection Male Check no default value in a dropdown I expect dropdown <DROPDOWN LABEL> to have no selection <VALUE NOT TO BE SELECTED ALREADY> Example: And I expect dropdown Gender to have no selection Random Check for absence of value in a dropdown I expect dropdown <DROPDOWN LABEL> to have no option <VALUE NOT TO BE PRESENT> Example: And I expect dropdown Gender to have no option Random Dropdown is readonly (cannot change the value in the dropdown) I expect dropdown <DROPDOWN LABEL> to be read-only Example: And I expect dropdown State to be read-only (Note: the hyphen between read and only) Dropdown should not be present on the screen I do not expect dropdown <DROPDOWN LABEL> Note: Alternatively you could have used I do not expect text <DRODOWN LABEL> but then it is not very intuitive TODO: Placeholder value check |
Checkbox
| Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|
| 1. Checkbox is selectable or not 2. Check if the checkbox selection enables the specific element as selected by mouse pointer 3. Check if the checkbox selection enables the specific element as selected by keyboard selection 4. Check if the checkbox is selected and pressing submit redirects to the option as per the choice made. 5. Uncheck the checkbox and click again to validate that the checkbox is checking and unchecking correctly 6. Check if the checkbox alignment on the form page is proper or not. 7. Check if the label for the checkbox is properly aligned. 8. Check if the corresponding data is selected by the database based on the selection. 9. Check if the validation controls enabled or triggered if no user action is done on the choices. 10. Verify if the initial focus of the checkbox is on the first checkbox. 11. Verify if the checkboxes (if multiple) are in the right order. 12. Look/positioning similar to UX design system (or as specified in the catalog) | Click Checkbox I click checkbox <CHECKBOX LABEL> Example: And I click checkbox I understand I am above 18 years Validate check box is checked already – (Prepopulated field/Default value) I expect checkbox <CHECKBOX LABEL> to be checked Example: And I expect checkbox I understand I am above 18 years to be checked Validate check box is not checked already- (Prepopulated field/Default value) I expect checkbox <CHECKBOX LABEL> to be unchecked Example: And I expect checkbox I understand I am above 18 years to be unchecked Checkbox is readonly – (cannot change the value) I expect checkbox <CHECKBOX LABEL> to be read-only Example: And I expect checkbox I understand I am above 18 years to be read-only (Note: the hyphen between read and only) Checkbox should not be present on the screen I do not expect checkbox <CHECKBOX LABEL> Note: Alternatively you could have used I do not expect text <CHECKBOX LABEL> but then it is not very intuitive Example: And I do not expect checkbox I understand I am above 18 years to be read-only |
Menu
| Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|
| 1. Type of menu based on requirements 2. Clicking of menu takes you to the right page 3. If mega menu a. Clicking the down arrow or clicking the menu item displays the mega panel b. Mega panel is not congested and displays properly c. Mega panel is center aligned 4. Alignment and spacing among the contents (ensure that it is not congested and properly displayed) 5. Look/positioning similar to UX design system (or as specified in the catalog) | Click menu I click menu <MENU OPTION> Example: And I click menu Do it Online And I click menu Search for a Professional |
Accordion
| Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|
| 1. Verify if the accordion opens the content of the section clicked. 2. If multiple accordions on the page verify if the accordion hides the content which is not clicked. 3. Check if the accordion accepts the mouse click action (or mouse hover – TODO) 4. Check if the sections are sort-able. 5. Verify if the expanding of the section does not break any other elements on the page. 6. Verify the default state of all the collapsed sections of the accordion widget are maintained. 7. Check if this state of the accordion is as per the specification for the webpage. 8. Check if the sections of the accordion are logically arranged as expected. 9. Check if the sections toggle properly. 10. Check if the behavior of the toggle is limited to the section and doesn’t interfere with the entire placing of the accordion. 11. Check if the all the sections can be expanded and close back again. 12. Look/positioning similar to UX design system (or as specified in the catalog) | Click accordion to expand I click accordion-section-title <ACCORDION-SECTION-TITLE> Example: And I click accordion-section-title Contact Details Note: Accordion section title appears as a clickable link and so we click on it to expand it. As a result the step definition I click link <ACCORDION-SECTION- TITLE> will also work. However it is not very intuitive |
Repeater
| Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|
| 1. Adding a repeater 2. Clicking done results in the value showing correctly as per the catalog 3. Edit the value in the repeater. New value is shown 4. Delete the value in the repeater.Maximum limit on repeater entries (if applicable as per catalog)Check that the repeater type is as per the specification (ex: Slideout, Modal, Inline)Look/positioning similar to UX design system (or as specified in the catalog) | Add an entry In the example we want to add multiple Other names (Label for the repeater is Other name)Note: For repeaters we do not need to add steps to click the Add button or Done button. The item is added using the label for the repeater and the step I add new This step looks for an HTML using the CSS selector containing “[data-button-action=’add’]”. #Name 1 And I add new Other name And I enter text FirstnameA in Given name And I enter text MiddlenameA in Other given names And I enter text LastnameA in Family name #Name 2 And I add new Other name And I enter text FirstnameB in Given name And I enter text MiddlenameB in Other given names And I enter text LastnameB in Family nameEdit an entry TODO: Delete an entry TODO: Edit an entry |
Tabs
| Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|
| 1. Exact spelling as per catalog 2. Exact casing as per catalog (title case vs sentence case) 3. Check that the tab type is as per the specification (ex: Horizontal, Secondary, Left, Right) 4. Look/positioning similar to UX design system (or as specified in the catalog) | Click Tab And I click tab <TAB NAME> Note: In the Verne context tabs will mostly be present on the View screens |
Expander
| Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|
| 1. Verify clicking the expander opens the content of the section clicked 2. Check if the expander accepts the mouse click action (or mouse hover – TODO) 3. Verify if the expanding of the section does not break any other elements on the page. 4. Check if the state of the expander is as per the specification for the webpage. 5. Check if the all the sections under the expander are present 6. Check that the expander can be expanded and close back again. 7. Look/positioning similar to UX design system (or as specified in the catalog) | Click expander to expand And I click expander <EXPANDER NAME> Example: And I click expander What is this TODO – Clicking the expander to expand. Clicking it again collapses it. (??) Check that the sections under the expander are not visible And I click expander <EXPANDER NAME> And I click expander <EXPANDER NAME> Example: And I click expander What is this And I click expander What is this And I do not expect text Names can be reserved either for use for a business name or a domestic or foreign company. |
Alerts
| Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|
| 1. Alert message triggered by the right condition (ex-Mandatory field validation, Business rule validation) 2. Alert message has the exact spelling as per catalog 3. Alert message has the exact casing as per catalog (title case vs sentence case) 4. Alert message wraps around correctly if too long 5. Right color shown for the alert message 6. Look/positioning similar to UX design system (or as specified in the catalog) | Note: Alerts can be at a screen level and at a node level Validate presence of alert message at the screen level I expect info message <INFO MESSAGE> I expect warning message <WARNING MESSAGE> I expect error message <ERROR MESSAGE> Example: And I expect info message I am Info And I expect warning message I am Warning And I expect error message I am Error Validate presence of alert message at the node level Note: Easy way of triggering it is clicking the submit/continue button without filling in any of the fields on the screen. At a node level this step will not work if the field only has a placeholder and not a label I expect <LABEL OF NODE> to have info message <INFO MESSAGE> I expect <LABEL OF NODE> to have warning message <WARNING MESSAGE> I expect <LABEL OF NODE> to have error message <ERROR MESSAGE> Example: And I expect Date of birth to have info message Must be older than 18 years And I expect Given name to have warning message Given name must be entered And I expect Last name to have error message Last name must be entered Validate absence of alert message at the screen level I do not expect info message <INFO MESSAGE> I do not expect warning message <WARNING MESSAGE> I do not expect error message <ERROR MESSAGE> Example: And I do not expect info message I am Info And I do not expect warning message I am Warning And I do not expect error message I am Error Validate absence of alert message at the node level I do not expect <LABEL OF NODE> to have info message <INFO MESSAGE> I do not expect <LABEL OF NODE> to have warning message <WARNING MESSAGE> I do not expect <LABEL OF NODE> to have error message <ERROR MESSAGE> Example: And I do not expect Date of birth to have info message Must be older than 18 years And I do not expect Given name to have warning message Given name must be entered And I do not expect Last name to have error message Last name must be entered |
Components
Document Upload
| Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|
| 1. Test the phrase upload is correctly aligned 2. Verify, a window is opened once this upload button is clicked. 3. Cancel button works during the upload process. 4. Only the particular file types can be uploaded as per catalog (ex. doc or pdf, or image files like jpeg, bmp, png etc) 5. Verify filename after file is uploaded. 6. Verify uploaded file cannot exceed a certain size as per catalog. For example, uploaded file cannot exceed 2 MB size. 7. Make sure, multiple file upload is working properly if it is an applicable scenario 8. Verify, the progress of upload function is working properly in case of big file sizes. 9. Make sure file upload process can resume, in case of network connectivity problem. (Once the problem is rectified) 10. Test empty upload is not working (if applicable). 11. Verify multiple uploads of the same file is not allowed (if applicable). 12. Make sure a new copy of the uploaded file is created to avoid overwriting. 13. Test drag and drop file options to upload is working properly besides the traditional way of uploading. 14. Once the file is uploaded or error in uploading, proper redirection happens. 15. Once the file is uploaded file can be removed and added again. Validate uploaded filename is intuitive. 16. Look/positioning similar to UX design system (or as specified in the catalog) | Upload document And I upload file <RELATIVE FILE PATH IN FILE SYSTEM> to <LABEL OF DOCUMENT UPLOAD> Example: And I upload file registry/common/tests/hercules/resources/uploads/test.pdf to Upload Documents Note: For the step definition to work the files to be tested needs to be committed to the source control system. Path needs to be specified to the file (note that it is not /registry/common but registry/common/ for the tests to work on Jenkins) Upload document section not present on the screen And I do not expect upload-section <LABEL OF DOCUMENT UPLOAD> Example: And I do not expect upload-section Supporting Documents |
Filings
| Functional Test Scenarios | Applicable Hercules Test Steps |
|---|---|
0
