HipTest Publisher

Web Interface

Export your code

Enter your Hiptest project secret token* You can find the secret token in the settings page of your project in Hiptest

Choose your export language and framework

Enter test run id or name Note: do not use a test run based export to automate your tests. Only use this option in conjunction with a CI tool

Filter on

Filter value

Only exports selected folders, not their children. Used in conjunction with filter-on-folder-ids or filter-on-folder-name

Select which category of items will be exported

Features
Stories
Steps definitions
Tests
Action words

Note: selecting none will do the default export with all data

Split each scenario in a single file

Create a directory structure Each folder in Hiptest will be a directory in the filesystem. Last level folder will be a test file

Keep the same filenames as in Hiptest Note: this may cause export issues when using special characters

Keep the same folder names as in Hiptest Note: this may cause export issues when using special characters

Export empty folders

Keep last-level action words only Hiptest will interpret the scenarios and only keep last-level action words

Do not export UIDs Gherkin export only: do not export UIDs for scenarios and datasets. Note that this might cause issues when pushing the results back to hiptest

Do not inherit parent tags Gherkin export only: do not inherit tags from parent folders

Export dataset names Gherkin export only: export the dataset names in a column for scenario examples

HipTest Publisher

Web Interface

Export your code

For your CI

Filter exported items

Select files to export

Structure export

Miscellaneous options