Best PracticesFeature File Review Check List

Feature File Review Check List

The following table provides you a checklist to be followed for Feature File:

Sl. NoTask listStatus
1Are 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?
Y/N status column
2Are you avoiding creating Duplicate Feature names?
Y/N status column
3Are you using appropriate page names in the navigations section instead of the current screen?
Y/N status column
4Are you using appropriate action words (default and custom actions) for the action being performed by the user?
Y/N status column
5Are you using intermittent verification steps?
Y/N status column
6Are you ensuring that UI elements linked to different actions have unique names during node configuration?
Y/N status column
7Are you avoiding duplicate UI Elements/ Control names?
Y/N status column
8Are 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?
Y/N status column
9Are you providing meaning scenario name and outline while recording a scenario using Follow Me feature?
Y/N status column
10Are you using the alias step if you wish to add or edit a GWT step manually in the Follow Me and Edit Scenarios features, if required?
Y/N status column
11Are you using the alias name for the control type in the Follow Me and Edit Scenarios features, if required?
Y/N status column
12Are you using Auto Generate test cases feature to generate test cases ?
Y/N status column
13Are you generating separate feature files with a module name?
Y/N status column
14Are you generating a single test case with multiple data sets instead of creating duplicate test cases for different data set?
Y/N status column
15When verifying the state of elements on the page, are you using "Verify content" action instead of "Verify displayed" and "Verify Text" actions?
Y/N status column
16Are you providing appropriate page names in navigations section instead of current screen ?
Y/N status column
17Are you generating negative scenarios using Data Generation option?
Y/N status column