Skip to main content

What's New in Vedro v1.7

· 2 min read

We're excited to announce Vedro v1.7, our latest release. This update brings new features and important fixes to enhance your testing experience. Let's take a closer look at what's new.

New Features

[Repeater] New Plugin Added

In our continuous effort to assist developers in creating robust and reliable tests, we've introduced the Repeater plugin in the core. The Repeater allows each test to be run N times, a feature that will help in detecting flaky tests early in the development process.

You can use the command line to set the number of repeats. Here's how you can do that:

$ vedro run --repeats 2
# or
$ vedro run -N 2

Here's a sample output demonstrating how tests are run twice using the Repeater:

✔ create user

├─[1/2] ✔ create user (0.20s)

├─[2/2] ✔ create user (0.20s)

✔ delete user

├─[1/2] ✔ delete user (0.10s)

├─[2/2] ✔ delete user (0.10s)

# --seed 1658e13e-2b3f-4f69-9132-cf8051ed018f
# repeated x2

# 2 scenarios, 2 passed, 0 failed, 0 skipped (0.40s)

[Rich Reporter] show_skipped Param Added

We've added a new show_skipped parameter to the Rich Reporter. By default, this parameter is set to True, allowing you to see the skipped tests in the report.

Here's a sample output showing the test report with skipped tests:

✔ create user (0.20s)
✔ delete user (0.10s)
○ update user (0.00s)

# --seed 3de2f365-bd1b-4eb0-8bc8-9f5432cabad5
# 3 scenarios, 2 passed, 0 failed, 1 skipped (0.30s)


[PyCharm Reporter] show_skipped Default Altered

In alignment with the addition made to the Rich Reporter, we've also adjusted the show_skipped parameter in the PyCharm Reporter. It's now set to True by default, enabling visibility for skipped tests.

Bug Fixes

[Core] @context Decorator Fixed

We've addressed a bug related to the type of the @context decorator. The correction ensures the accuracy and proper functionality of the decorator.

[Core] Deferrer and Artifacted Order Fixed

The registration order of the Deferrer and Artifacted plugins was found to be incorrect, which could have led to potential issues. We've corrected this in Vedro v1.7 to ensure smoother plugin operation.


For the latest news and updates, subscribe to our Telegram or Twitter