Import feature file
Hiptest enables you to upload feature files written using Gherkin syntax (Cucumber, SpecFlow…)
NOTE: This feature is available only for projects that belong to an organization with a Pro subscription.
In your project settings, activate the BDD mode option.
This will enable the step editor to interpret the Gherkin syntax and only action words (reusable steps) will be created.
For a good project organization, your features are managed with folders.
After activating the BDD mode, in the folder page, new actions appear:
You can upload your feature files by selecting one of the actions or using the drag-and-drop function.
Note: Only “.feature” extension is accepted. Otherwise an error will be displayed.
The “Create from feature file” action and the drop zone will first look for existing subfolders with the same name as the features you are importing.
If none can be found then new subfolders are created under the current folder. They represent the imported features with their descriptions, tags, scenarios, scenario outlines, examples…
And using the “Update from feature file” action, the existing folder will be updated with the feature file you are importing. For this purpose, a window will show you which updates are about to be done:
Click on “Apply changes” once you review them to update your folder and scenarios.
The Gherkin steps will be converted into action word calls. If the action word does not exist, it will be created.
If there is an existing folder with the same name in the same hierarchy level, the new folder name will be suffixed with a number. For example, an existing folder is named “Support internationalisation”, the new one will be named “Support internationalisation (1)”.
If one or more scenarios in your folder are not present in the .feature file, they will remain in your folder unless you check the option to delete them.
In that case, they will be permanently deleted from your folder.
When updating a folder from a feature file that contains scenario outlines with examples, datatables of impacted scenarios will be updated accordingly.
If the first column of your Gherkin examples is named “Dataset name”, it will be used to name your datasets. If you already have datasets with those names they will be updated.
If you do not have a “Dataset name” column in your examples, datasets are retrieved based on their values. If a value has changed, the corresponding dataset will not be found so a new one will be created and the old one will be deleted.