Plugins
Explore Vedro’s plugin ecosystem, which consists of core plugins providing essential features and community-developed plugins that extend its functionality. Discover how to integrate these plugins into your project, and enhance your testing experience with the wide range of tools available.
New to using plugins in Vedro? Check out our Using Plugins guide to learn how to install, configure, and manage plugins in your project.
Community Plugins
The Vedro community actively contributes to the framework by developing plugins that expand its capabilities. Below is a list of popular third-party plugins that add various features like enhanced reporting and integrations:
| Plugin | Description | Info |
|---|
Looking for more plugins? Explore the full list on PyPi.
Interested in creating custom plugins? Learn how to develop your own in the Writing Plugins guide.
IDE Plugins
These plugins integrate Vedro with popular Integrated Development Environments (IDEs), providing seamless workflows and a more user-friendly experience.
| Plugin | Description | Info |
|---|---|---|
| PyCharm Plugin | Integration with PyCharm for easy scenario execution and debugging. | Version 0.2.5 |
| VSCode Extension | Adds Vedro support to VSCode, allowing easy test runs and result viewing. | Version 0.1.1 |
Core Plugins
Vedro comes with a rich set of built-in plugins that provide essential testing features. These plugins are designed to improve scenario management, reporting, and test execution, ensuring a flexible and robust testing experience.
| Plugin | Description | Info |
|---|---|---|
| Director | Manages and configures reporters for scenario execution |  |
| Rich Reporter | Enhanced, customizable scenario reporting with rich output | |
| Silent Reporter | Minimizes output during scenario execution | |
| PyCharm Reporter | Outputs scenario results in a PyCharm-friendly format | |
| Orderer | Configures the execution order of scenarios | |
| Deferrer | Executes deferred functions at the end of each scenario | |
| Artifacted | Manages artifacts for step and scenario results | |
| Interrupter | Halts test execution after N failed scenarios or on specified signals | |
| Seeder | Sets seeds for deterministic random behavior in scenarios | |
| Skipper | Allows selective scenario skipping and selection based on file/directory or subject | |
| Slicer | Provides a way to distribute scenarios among multiple workers | |
| Tagger | Allows scenarios to be selectively run based on user-defined tags | |
| Repeater | Repeat scenarios a specified number of times | |
| Rerunner | Reruns failed scenarios a specified number of times | |
| AssertRewriter | Rewrites assert statements to provide better error messages | |
| DryRunner | Simulates scenario execution without actually executing them | |
| Ensurer | Adds configurable retry logic to functions and steps, including attempts, delay and exceptions to swallow | |
| LastFailed | Runs only the previously failed scenarios | |
| TempKeeper | Manages temporary directories and files | |
| Terminator | Handles test exit status based on test results and interruptions | |
Feedback
We are continuously working to improve Vedro and its ecosystem. If you have suggestions for new plugins or improvements to existing ones, please open an issue on our GitHub repository or reach out to us on Twitter with your ideas!