You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage python3-pytest-randomly-3.11.0-2.fc36.noarch
Pytest plugin to randomly order tests and control random.seed.
RPMPackage python3-pytest-plus-0.2-1.lbn36.noarch
PyTest Plus Plugin :: extends pytest functionality[![PyPI version]( [![Python versions]( [![Python Black Code Style]( plugin aims to be used to host multiple pytest extensions that meet the following criteria:* Keep py27 compatibility for the moment * Downgrade gracefully, meaning that if the plugin is removed, you will still be able to run pytest PYTEST_REQPASS
RPMPackage python3-pytest-playwright-0.4.4-1.lbn36.noarch
Pytest plugin for Playwright [![PyPI]( end-to-end tests for your web apps with [Playwright]( and [pytest]( Support for **all modern browsers** including Chromium, WebKit and Firefox. - Support for **headless and headed** execution. - **Built-in fixtures** that provide browser primitives to test functions. DocumentationSee on [playwright.dev]( for examples and more detailed information.
RPMPackage python3-pytest-perf-0.14.0-1.lbn36.noarch
Run performance tests against the mainline code. Usage To use it, include pytest-perf in the test dependencies for your project, then create some Python module in your package. The plugin will include any module that contains the text “pytest_perf” and will run performance tests on each function containing “perf” in the name. Tests don’t execute the module directly, but instead parse out the code of the function in two parts, the warmup and the test, separated by a “# end warmup” comment, and then passes those to the timeit module. See the exercises.py module for example usage. Design pytest-perf works by creating two installs, the control and the experiment, and measuring the performance of some python code against each. Under the hood, it uses pip-run to install from the upstream main branch (e.g. https:/github.com/jaraco/pytest-perf) for the control and from . for the experiment. It then runs each of the experiments against each of the enviroments.
RPMPackage python3-pytest-pep8-1.0.6-1.lbn36.noarch
py.test plugin for efficiently checking PEP8 compliance Usage install via:: pip install pytest-pep8if you then type:: py.test --pep8every file ending in .py will be discovered and pep8-checked, starting from the command line arguments. .. warning:: Running pep8 tests on your project is likely to cause a lot of issues. This plugin allows to configure on a per-project and per-file basis which...
RPMPackage python3-pytest-param-files-0.3.4-5.lbn36.noarch
A package to generate parametrized pytests from external files. Create a text file with the dot format, then use the `param_file` pytest marker to create a parametrized test.
RPMPackage python3-pytest-ordering-0.6-8.fc36.noarch
pytest-ordering is a pytest plugin to run your tests in any order that you specify. It provides custom markers that say when your tests should run in relation to each other. They can be absolute (i.e. first, or second-to-last) or relative (i.e. run this test before this other test).
RPMPackage python3-pytest-order-1.2.0-1.lbn36.noarch
_pytest-order_ - a pytest plugin to order test execution [![PyPI version]( [![Testsuite]( [![DocBuild]( [![codecov]( [![Python version](
RPMPackage python3-pytest-openfiles-0.5.0-6.fc36.noarch
The pytest-openfiles plugin allows for the detection of open I/O resources at the end of unit tests. This is particularly useful for testing code that manipulates file handles or other I/O resources. It allows developers to ensure that this kind of code properly cleans up I/O resources when they are no longer needed.
RPMPackage python3-pytest-mypy-plugins-1.9.3-1.lbn36.noarch
<img src" alt"mypy logo" width"300px"/> pytest plugin for testing mypy types, stubs, and plugins[![Tests Status]( [![Checked with mypy]( [![Gitter]( [![PyPI](
RPMPackage python3-pytest-mypy-0.9.1-1.lbn36.noarch
pytest-mypy Mypy static type checker plugin for pytest --* Runs the mypy static type checker on your source files as part of your pytest test runs. * Does for mypy_ what the pytest-flake8_ plugin does for flake8_. * This is a work in progress – pull requests appreciated. Installation You can install "pytest- mypy" via pip_ from PyPI_:.. code-block:: bash $ pip install pytest-mypyUsage You can...
RPMPackage python3-pytest-multihost-3.0-16.fc36.noarch
Allows pytest tests to run commands on several machines. The machines to run on are described on the command line, the tests specify how many machines they need and commands/checks to run on them.
RPMPackage python3-pytest-mpl-0.13-3.fc36.noarch
This is a plugin to facilitate image comparison for Matplotlib figures in pytest. Matplotlib includes a number of test utilities and decorators, but these are geared towards the nose testing framework. Pytest-mpl makes it easy to compare figures produced by tests to reference images when using pytest.
RPMPackage python3-pytest-metadata-1.7.0-8.fc36.noarch
Pytest plugin that provides access to test session metadata
RPMPackage python3-pytest-localserver-0.6.0-1.fc36.noarch
pytest-localserver is a plugin for the pytest testing framework which enables you to test server connections locally.
RPMPackage python3-pytest-lazy-fixture-0.6.3-5.fc36.noarch
Use fixtures in pytest.mark.parametrize.
RPMPackage python3-pytest-isort-2.0.0-2.fc36.noarch
py.test plugin to check import ordering using isort.
RPMPackage python3-pytest-integration-0.2.3-1.lbn36.noarch
pytest-integration OverviewPlugin for [pytest]( to mark tests as integration or slow integration.Integration tests are run after normal tests (unit tests) and slow integration tests are run after (quick) integration tests.If a unit test fails, (quick) integration and slow integration tests are not run.If a (quick) integration tests fails, slow integration tests are not run.If you have also...
RPMPackage python3-pytest-httpx-0.18.0-1.fc36.noarch
httpx_mock pytest fixture will make sure every httpx request will be replied to with user provided responses.
RPMPackage python3-pytest-httpserver-1.0.4-1.fc36.noarch
This library is designed to help to test http clients without contacting the real http server. In other words, it is a fake http server which is accessible via localhost can be started with the pre-defined expected http requests and their responses.