The following table provides you a checklist for a Feature File:
| Sl. No | Task list | Status |
| 1 | Are you providing meaningful names to Features (Tabs within a screen or a page) and Controls (UI elements on the page in the tab) in the lower case? |  |
| 3 | Are you avoiding creating Duplicate Feature names? |  |
| 4 | Are you using appropriate page names in the navigations section instead of the current screen? |  |
| 5 | Are you using appropriate action words (default and custom actions) for the action being performed by the user? |  |
| 6 | Are you using relative XPaths? |  |
| 7 | Are you using intermittent verification steps? |  |
| 8 | Are you ensuring that UI elements linked to different actions have unique names during node configuration? |  |
| 9 | Are you avoiding duplicate control names? |  |
| 10 | Are you adding parameters for Text Box, Dropdown list, Text Area, Scroll, Window and New Tab in the 'Control Value' text box to specify input variations? |  |
| 11 | Have you enabled Deduplication option to generate test cases in separate YAML file? |  |
| 12 | Are you using alias name for the control type in Follow Me and Edit Scenarios features, if required? |  |
| 13 | Are you generating separate feature files with a module name? |  |
| 14 | When verifying the state of elements on the page, are you using "Verify content" action instead of "Verify display" and "Verify Text" action? |  |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article