- Behave - Discussion
- Behave - Useful Resources
- Behave - Quick Guide
- Behave - Debugging
- Behave - Hooks
- Behave - Reports
- Behave - Retry Mechanism
- Behave - Exclude Tests
- Behave - Runner Script
- Behave - Step Parameters
- Behave - Step Functions
- Behave - Multi-Methods
- Behave - Optional Part
- Behave - Regular Expressions
- Behave - Step Matchers
- Behave - Enumeration
- Behave - Tags
- Behave - Data Types
- Behave - Background
- Behave - Steps in a Step
- Behave - Setup Table
- Behave - Multiline Text
- Behave - Scenario Outlines
- Behave - Step Parameters
- Behave - Supported Languages
- Behave - First Steps
- Behave - Step Implementations
- Behave - Feature Files
- Behave - Gherkin Keywords
- Behave - Feature Testing Setup
- Behave - Configuration Files
- Behave - Command Line
- Behave - Installation
- Behave - Introduction
- Behave - Home
Selected Reading
- Who is Who
- Computer Glossary
- HR Interview Questions
- Effective Resume Writing
- Questions and Answers
- UPSC IAS Exams Notes
Behave - Retry Mechanism
We can rerun failed Scenarios in the feature file in Behave. This is taken care with the help of the formatters.
All the available formatters in Behave can be seen with the command given below −
behave –f help
You can see the following screen after using the command −
The rerun formatter is used to capture the faipng scenario and output it in a separate file. Let us take an example, where we have 1 failed feature.
Then capture the failed feature in another feature file with the command −
behave –f rerun –o failed_features.feature
You can see the following −
The failed_features.feature file gets generated within the project. It contains the feature file name Payment1.feature where we have a failure.
To re-trigger only failed Scenario, we have to run the command stated below −
behave @failed_features.feature
You will see the following screen −
Advertisements