Repositories Tree View

The Repositories panel on the left-hand side shows your repository hierarchy and lets you manage folders, Test Sets, feature files, step definitions, and payloads - all from a single tree view.

Tree Structure

• Folder
  A container for Test Sets or nested folders.
• Test Set
  A suite of related feature files and step definitions.
• Feature File
  A .feature file containing scenarios.
• Step File
  A reusable set of test commands.
• Payload
  (Test Set only) An XML or JSON payload used for AireGlu or AireFlow testing.
• Files
  (Test Set only) A folder of files a test can upload into a file upload control. It only appears once the Test Set has at least one file.

Filtering the Tree

On a large repository it can be quicker to filter the tree than to expand your way down to a file. Select the magnifying glass at the top of the Repositories panel to show the filter box, and type any part of the name you are looking for.

• Matching is on names only - folders, Test Sets, feature and step files, payloads and uploaded files. It is not case-sensitive, and matches any part of a name, so book finds rebooking.feature.
• Folders containing a match open automatically, so a file nested several levels down appears without any expanding.
• Matching a folder or Test Set keeps everything inside it, so you can open it up and browse as usual - a quick way to narrow the tree to one area.
• The file you have open stays open in the editor even when the filter hides it from the tree.
• Select the magnifying glass again (or press Esc) to hide the box. While the box is hidden no filter is applied, and the tree returns to exactly the folders you had open before.

Context-Menu Actions

Select the 3 dots on any node in the tree to perform the following actions:

1. Add Folder

Creates a new folder under the selected node.

• Use folders to keep your Test Sets organised.

2. Add Test Set

Adds a new Test Set under the selected folder. This option is only available when selecting a folder

• This will need to be configured (see File and Test Set Settings)

3. Add Feature File

Creates a new .feature file inside the selected Test Set.

4. Add Step File

Adds a new step-definition file alongside the selected feature folder.

5. Delete

Removes the selected node (folder, Test Set, feature file, step file, or payload).

• A confirmation prompt will appear before deletion.

Test-Set-Specific Actions

When you select a Test Set node, two additional options appear in the context menu:

• Add AireGlu Payload

Creates a new payload template file in AireGluPayloads/.

• Use this for testing API-driven flows against your AireGlu instance.

• Add AireFlow Payload

Creates a new payload template file in AireFlowPayloads/.

• Use this for triggering workflows or events in AireFlow.

• Add File

Chooses a file from your computer and adds it to the Test Set's Files/ folder, for a test to upload into a file upload control (see AireForm Commands), or to fill a Scenario Outline's Examples (see Data-Driven Scenarios).

• This action is on both the Test Set and the Files node, because Files only exists once the Test Set has a file in it.
• Selecting a file previews it: images are shown, and text-based files such as .json, .xml and .txt open read-only. To change a file's contents, delete the old one and add it again.
• Rename a file the same way as any other - select it and edit File name in the settings panel.
• There is a maximum file size and a list of allowed file types, both set by your administrator. Runnable files are never allowed. A file that is too large or of the wrong type is rejected as soon as you choose it.

Saving Changes

Once you’ve finished editing the tree view, click Save Changes (or Reset to revert changes) at the bottom of the Test Editor, you will be prompted for a commit message before saving to summarise the changes.