Generating Separate Feature Files in a Separate Folder for API Automation

Modified on Tue, 13 Aug at 10:50 AM

TABLE OF CONTENTS

1. Overview

2. Generating Feature Files in a Separate Folder

3. Adding a Separate Feature 

3. Consolidated Feature Files for Multiple Collections

1. Overview

This article outlines the process for generating and managing feature files for API test automation.

If you are working with different modules of user actions, such as create a user or create a profile, you can generate separate feature files. These files outline specific behaviors of the application. Each file will be organized into designated folders based on their module.

2. Generating Feature Files in a Separate Folder

To generate feature files with a separate feature name within a separate folder, perform the following:
Make sure to select the 'Requirement Filter' option' in the Project Settings page and click Submit, as shown:


3. Adding a Separate Feature 

  1. In the Main Canvas, search for the appropriate API test automation in the Project Explorer.
  2. In the left pane of API testing page, select the appropriate API collection and right-click to select Separate Feature option, enter a name and click Submit, as shown:

  3. The Feature File will be generated module-wise in the Test Cases folder, as shown. To access the feature file, navigate to the appropriate project folder and expand the Test Cases Folder in the Project Explorer.

  4. If you don't provide the name for the particular request and still wish to generate a separate Feature file and Requirement option is checked, then it will be generated in the Request name provided.

3. Consolidated Feature Files for Multiple Collections

  1. Assigning Feature Names:
    When you create collections and assign a specific feature name (for example., "User Authentication and Management") to each collection, the system generates a consolidated Feature File, as shown:

  2. Viewing the Consolidated Feature File:

    This Feature File, named according to the provided feature name, will include a comprehensive list of all scenarios from the collections you specified.

    For example, if you have multiple collections and name them all with "User Authentication and Management," the resulting Feature File will aggregate all scenarios from these collections into a single file.

  3. Accessing the Feature File:

    Navigate to the Test Cases folder in the Project Explorer to view this consolidated Feature File.




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article