Pytest-failed-to-verify

Latest version: v0.1.5

Safety actively analyzes 613460 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

0.1.4

What's New
------------
* with this revision we are turning on the `failed-to-verify` test-outcome again (failed to verify tests will be correctly marked as failed to verify).
* all traceback information is displayed as supposed.

0.1.1alpha

What's New
------------

- temporarily turned off `failed to verify` result in order to make errors visible in the traceback (`failed to verify` tests will be marked as `failed`). This is a pre-release fix.

0.1.0

🎉🥳Very first release of the pytest plugin created to help us at gastrofix (and maybe also you) to fight flaky tests.

This plugin gives you a more detailed output on your pytest report to distinguish the following cases:
* `PASSED`: test passed without any errors
* `FAILED`: test failed with errors
* `FAILED TO VERIFY`: test failed to get to the call phase (the actual test was not run)

Additionally with this plugin you are able to enforce getting to the call phase of pytest by re-running a flaky setup phase multiple times on failure *but* not the whole test (consisting of setup+call+teardown).

This way you can make sure that your actual tested business logic is being executed and tested and only this way your tests actually provide any valuable outcome.

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.