All Collections
Frequently Asked Questions (FAQ)
Behave Pro
Does Behave Pro Have a Feature File Limit?
Does Behave Pro Have a Feature File Limit?

Avoiding limits of Git provider API's

Alan Parkinson avatar
Written by Alan Parkinson
Updated over a week ago

Performance impacts can arise from limitations imposed by the API of git providers, as a result if you are using a classic style project there are no limitations to how many feature files you can have

Behave Pro does not necessarily have any limits on the amount of scenarios or features you have within Behave Pro. However, with a Git integrated project you may start to notice issues such as performance impacts and missing features when reaching around 1000 features. This unfortunately is due to operation limits set by Git providers, as a result we strongly recommend to keep the number of features below this number. If you are struggling to have a feature count below this number, below are some tips to try and decrease the amount.

Feature File Directory

During setup of Behave Pro you will need to specify a branch and directory for where feature files can be found as shown below. Within this feature file directory, it's best to only store feature files as we will need to check all files within this directory (and all subdirectories) to find feature files for Behave Pro to display in Requirements. In addition, if feature files are not being used anymore and you are hitting performance impacts when using the Requirements page you may want to consider removing any that you may no longer be using.

Seperate Repositories

If you have multiple projects it would be best to keep these seperated in seperate repositories, this helps to ensure that there isn't an excessive number of feature files that will require being read and displayed in your requirements page.

Reducing Features Used

It's worth remembering that features and scenarios are not designed to have a one-to-one relationship and features are a documentation of your applications functionality. It's worth looking at this article to understand the difference between your user stories, features and scenarios.

Did this answer your question?