pytest7.4版本的一个变更,可能会影响你的项目

pytest7,版本,一个,变更,可能,影响,项目 · 浏览次数 : 213

小编点评

当不指定--confcutdir时,conftest截断目录(--confcutdir)现在被设置为[rootdir](https://docs.pytest.org/en/7.4.x/reference/customize.html#rootdir)。在以前的情况下,conftest.py文件会一直被探测到文件系统的根目录。 如果未指定--confcutdir,pytest会默认使用根目录作为搜索的根目录。因此,在不指定--confcutdir的情况下,pytest会搜索到根目录下的conftest.py文件。 如果想要指定 conftest截断目录的搜索根目录,可以使用命令行参数 --confcutdir。例如: ``` pip install pytest --confcutdir=.. ``` 这个参数会在 pytest 的安装过程中被设置。 如果想要在项目根目录下指定 conftest截断目录,可以使用 pytest.ini文件中的 addopts 参数。例如: ``` [pytest] pytest --confcutdir=\"D:\\Gitee\\DemoRepo\" ``` 这个参数会在 pytest 的安装过程中被设置。 此外,如果想要在项目根目录下指定 conftest截断目录,可以使用 pytest.ini文件的 addopts 参数。例如: ``` [pytest] pytest --confcutdir=\"D:\\Gitee\\DemoRepo\" ```

正文

pytest7.4版本的一个变更,可能会影响你的项目

本文撰写于 2023.7.10

准备工作

  • 项目结构如下

    D:\Gitee\DemoRepo (17.97MB)
    +-- testCases (1.03KB)
    |   +-- conftest.py (252b)
    |   +-- pmCases (574b)
    |   |   +-- conftest.py (259b)
    |   |   `-- test_logout.py (315b)
    
  • 顶层conftest.py内容

    import pytest
    
    @pytest.fixture(scope='session')
    def fix_all():
        print('fix_all')
    
  • pmCases下的conftest.py内容

    import pytest
    
    @pytest.fixture(scope='session', autouse=True)
    def fix_all2():
        print('fix_all2')
    
    
  • test_logout.py内容

    import pytest
    
    
    def test_logout(fix_all):
        print('test_logout')
    
    if __name__ == '__main__':
        pytest.main(['-sv',__file__])
    

Pytest7.4之前

用的Pytest7.3.1,而实际7.4.0之前也就只有一个7.3.2了

  • 你是可以执行test_logout.py的

  • 效果如下

    test_logout.py::test_logout fix_all2
    fix_all
    test_logout
    PASSED
    
  • 所以按照以前的认识

    • conftest可以存在多个
    • 测试用例可以看到上级目录的conftest
    • 但看不到下级目录的conftest(此处没有演示)

Pytest7.4.0

执行效果

注意把pytest更新到pytest7.4.0

  • 同样执行test_logout.py

  • 效果如下

    D:\Gitee\DemoRepo\venv\Scripts\python.exe D:/Gitee/DemoRepo/testCases/pmCases/test_logout.py
    ============================= test session starts =============================
    platform win32 -- Python 3.9.6, pytest-7.4.0, pluggy-1.2.0 -- D:\Gitee\DemoRepo\venv\Scripts\python.exe
    cachedir: .pytest_cache
    rootdir: D:\Gitee\DemoRepo\testCases\pmCases
    collecting ... collected 1 item
    
    test_logout.py::test_logout fix_all2
    ERROR
    
    =================================== ERRORS ====================================
    ________________________ ERROR at setup of test_logout ________________________
    file D:\Gitee\DemoRepo\testCases\pmCases\test_logout.py, line 10
      def test_logout(fix_all):
    E       fixture 'fix_all' not found
    >       available fixtures: cache, capfd, capfdbinary, caplog, capsys, capsysbinary, doctest_namespace, fix_all2, monkeypatch, pytestconfig, record_property, record_testsuite_property, record_xml_attribute, recwarn, tmp_path, tmp_path_factory, tmpdir, tmpdir_factory
    >       use 'pytest --fixtures [testpath]' for help on them.
    
    D:\Gitee\DemoRepo\testCases\pmCases\test_logout.py:10
    =========================== short test summary info ===========================
    ERROR test_logout.py::test_logout
    ============================== 1 error in 0.01s ===============================
    
    进程已结束,退出代码为 0
    
    
  • 很清楚的提示

    E       fixture 'fix_all' not found
    
  • 子目录无法去引用上级目录的fixture

  • 而同级目录不受影响

  • 我们的实战课就会用到子目录下的测试文件调用上级目录的fixture,是没问题的,但现在会受影响。

  • 这是为何呢?第一个想法就是版本变动了。但觉得不太可以理解,正常版本变动对这些逻辑不应该去大改,除非是大版本的改变。因为一旦出现这样的引用,你以前的项目会无法调用。


  • 很多的时候你是在终端下执行

  • 修改test_logout.py

    def test_logout(fix_all):
        print('test_logout')
    
  • 终端下执行

    D:\Gitee\DemoRepo\testCases>pytest
    # 这是成功的
    
  • 这样执行

    D:\Gitee\DemoRepo\testCases\pmCases>pytest
    # 报错跟上面一样  E       fixture 'fix_all' not found
    
    
  • 基于此,如果你是终端下执行的话,其实是没啥影响的。

  • 只有你要在子目录下测试或者单独执行子测试用例时可能会有问题


  • 带着这样的疑问去官方文档找原因。

changlog Of pytest 7.4.0

https://docs.pytest.org/en/7.4.x/changelog.html#

发布时间 (2023-06-23)

Features

Improvements

  • #10872: Update test log report annotation to named tuple and fixed inconsistency in docs for pytest_report_teststatus hook.

  • #10907: When an exception traceback to be displayed is completely filtered out (by mechanisms such as __tracebackhide__, internal frames, and similar), now only the exception string and the following message are shown:

    “All traceback entries are hidden. Pass --full-trace to see hidden and internal frames.”.

    Previously, the last frame of the traceback was shown, even though it was hidden.

  • #10940: Improved verbose output (-vv) of skip and xfail reasons by performing text wrapping while leaving a clear margin for progress output.

    Added TerminalReporter.wrap_write() as a helper for that.

  • #10991: Added handling of %f directive to print microseconds in log format options, such as log-date-format.

  • #11005: Added the underlying exception to the cache provider’s path creation and write warning messages.

  • #11013: Added warning when testpaths is set, but paths are not found by glob. In this case, pytest will fall back to searching from the current directory.

  • #11043: When --confcutdir is not specified, and there is no config file present, the conftest cutoff directory (--confcutdir) is now set to the rootdir. Previously in such cases, conftest.py files would be probed all the way to the root directory of the filesystem. If you are badly affected by this change, consider adding an empty config file to your desired cutoff directory, or explicitly set --confcutdir.

  • #11081: The norecursedirs check is now performed in a pytest_ignore_collect implementation, so plugins can affect it.

    If after updating to this version you see that your norecursedirs setting is not being respected, it means that a conftest or a plugin you use has a bad pytest_ignore_collect implementation. Most likely, your hook returns False for paths it does not want to ignore, which ends the processing and doesn’t allow other plugins, including pytest itself, to ignore the path. The fix is to return None instead of False for paths your hook doesn’t want to ignore.

  • #8711: caplog.set_level() and caplog.at_level() will temporarily enable the requested level if level was disabled globally via logging.disable(LEVEL).

Bug Fixes

  • #10831: Terminal Reporting: Fixed bug when running in --tb=line mode where pytest.fail(pytrace=False) tests report None.
  • #11068: Fixed the --last-failed whole-file skipping functionality (“skipped N files”) for non-python test files.
  • #11104: Fixed a regression in pytest 7.3.2 which caused to testpaths to be considered for loading initial conftests, even when it was not utilized (e.g. when explicit paths were given on the command line). Now the testpaths are only considered when they are in use.
  • #1904: Fixed traceback entries hidden with __tracebackhide__ = True still being shown for chained exceptions (parts after “… the above exception …” message).
  • #7781: Fix writing non-encodable text to log file when using --debug.

Improved Documentation

Trivial/Internal Changes

  • #11031: Enhanced the CLI flag for -c to now include --config-file to make it clear that this flag applies to the usage of a custom config file.

抓重点

  • 原文

    When `--confcutdir` is not specified, and there is no config file present, the conftest cutoff directory (`--confcutdir`) is now set to the [rootdir](https://docs.pytest.org/en/7.4.x/reference/customize.html#rootdir). Previously in such cases, `conftest.py` files would be probed all the way to the root directory of the filesystem. If you are badly affected by this change, consider adding an empty config file to your desired cutoff directory, or explicitly set `--confcutdir`.
    
  • 译文

    当未指定--confcutdir并且没有配置文件存在时,conftest截断目录(--confcutdir)现在被设置为rootdir。在以前的情况下,conftest.py文件会一直被探测到文件系统的根目录。如果你受到这个变化的严重影响,考虑在所需的截断目录中添加一个空的配置文件,或者明确地设置--confcutdir。
    

解决方式

  • 指定参数--confcutdir

  • 示例1: test_logout.py执行

    import pytest
    
    
    def test_logout(fix_all):
        print('test_logout')
    
    if __name__ == '__main__':
        pytest.main(['-sv','--confcutdir=..',__file__]) # 意思是设定conftest.py的搜索根目录是当前目录上级
    
  • 示例2: 终端执行

    # 你在pmCases下执行
    # 如果在项目根目录下,本来就是ok的
    pytest --confcutdir=..
    
  • 示例3: pytest.ini

    [pytest]
    # 改为实际的项目根目录即可
    addopts = --confcutdir="D:\Gitee\DemoRepo" 
    
    • 注意不要写成--confcutdir=.(因为你是把pytest.ini放在根目录下的)

补充说明

  • 截止到撰写本文的时候(2023-7-10)发现

  • pip install pytest会安装最新的Pytest7.4.0

  • 而通过pycharm安装则是Pytest7.3.1

  • 对于这个参数,命令行--help的解释是

      --confcutdir=dir      Only load conftest.py's relative to specified dir
    

与pytest7.4版本的一个变更,可能会影响你的项目相似的内容:

pytest7.4版本的一个变更,可能会影响你的项目

# pytest7.4版本的一个变更,可能会影响你的项目 > 本文撰写于 2023.7.10 # 准备工作 - 项目结构如下 ``` D:\Gitee\DemoRepo (17.97MB) +-- testCases (1.03KB) | +-- conftest.py (252b) | +-- p

浅谈Pytest中的marker

浅谈Pytest中的marker 没有注册marker 我们写一个简单的测试 # test_demo.py import pytest @pytest.mark.login def test_demo(): assert True 你运行的话会有如下提示 test_demo.py:4: Pytest

Pytest插件pytest-order指定用例顺序

Pytest插件pytest-order指定用例顺序 安装 pip install pytest-order 注意不是pytest-ordering 说起来这里有个故事 关于pytest-ordering和pytest-order https://github.com/ftobia/pytest-o

Pytest插件pytest-assume多重断言

Pytest插件pytest-assume多重断言 背景 import pytest def test_assume1(): assert 1 == 2 print('hello') assert 2 == 3 if __name__ == '__main__': pytest.main(['-sv

Pytest插件pytest-repeat重复执行

Pytest插件pytest-repeat重复执行 安装 pip install pytest-repeat doc https://pypi.org/project/pytest-repeat/ https://github.com/pytest-dev/pytest-repeat 2020年10

Pytest插件pytest-rerunfailures失败重跑

Pytest插件pytest-rerunfailures失败重跑 安装 pip install pytest-rerunfailures doc https://github.com/pytest-dev/pytest-rerunfailures https://pypi.org/project/p

浅谈Pytest中的warning处理

浅谈Pytest中的warning处理 没有处理warning 我们写一个简单的测试 import pytest def test_demo(): import warnings warnings.warn('test warn',DeprecationWarning) assert True if

详谈pytest中的xfail

详谈pytest中的xfail 原文链接: https://docs.pytest.org/en/7.2.x/how-to/skipping.html 链接中详细阐述了skip和xfail两种情况 xfail 应该译作expected fail,预期失败(我知道这个用例是因为某些原因会失败的) 有哪

【Playwright+Python】系列教程(四)Pytest 插件在Playwright中的使用

一、命令行使用详解 使用Pytest插件在Playwright 中来编写端到端的测试。 1、命令行执行测试 pytest --browser webkit --headed 2、使用 pytest.ini 文件配置 内容如下: [pytest] # Run firefox with UI addop

Python中的枚举类enum

0. 本文来历 上一篇文章,我写了Pytest插件pytest-order指定用例顺序 我当时就比较好奇它的顺序和英文的对应关系,肯定是写死的,找了下就发现在源码sorter.py中定义了一个dict如下 orders_map = { "first": 0, "second": 1, "third"