- Behave Tutorial
- Behave - Home
- Behave - Introduction
- Behave - Installation
- Behave - Command Line
- Behave - Configuration Files
- Behave - Feature Testing Setup
- Behave - Gherkin Keywords
- Behave - Feature Files
- Behave - Step Implementations
- Behave - First Steps
- Behave - Supported Languages
- Behave - Step Parameters
- Behave - Scenario Outlines
- Behave - Multiline Text
- Behave - Setup Table
- Behave - Steps in a Step
- Behave - Background
- Behave - Data Types
- Behave - Tags
- Behave - Enumeration
- Behave - Step Matchers
- Behave - Regular Expressions
- Behave - Optional Part
- Behave - Multi-Methods
- Behave - Step Functions
- Behave - Step Parameters
- Behave - Runner Script
- Behave - Exclude Tests
- Behave - Retry Mechanism
- Behave - Reports
- Behave - Hooks
- Behave - Debugging
- Behave Useful Resources
- Behave - Quick Guide
- Behave - Useful Resources
- Behave - Discussion
Behave - Exclude Tests
We can exclude the executing files by its filename from execution.
Suppose, we have more than one feature file within the features folder. The following screen can be seen on the computer −
On executing the command behave, the output will be as follows −
If we have to only run the feature file Payment.feature and exclude Payment1.feature, we have to pass the command line argument --e or --exclude followed by pattern of the regular expression.
On executing the command behave --exclude *1.feature, the output is as follows −
The output shows one feature passed along with the Payment.feature file name. Also, Payment1.feature is not included in the run.
Advertisements