Setting a fixture scope of "package" will not teardown the fixture

[hayleyday]

I am using Windows 10, Python 3.6, and pytest 3.7.1 or 3.7.0 (tested with both).

Here are the libraries I have installed:
atomicwrites 1.1.5
attrs 18.1.0
colorama 0.3.9
more-itertools 4.3.0
pip 9.0.3
pluggy 0.7.1
psutil 5.4.6
py 1.5.4
pyserial 3.4
pytest 3.7.1
setuptools 40.0.0
six 1.11.0
websocket-server 0.4

It appears as though when a fixture is setup with a scope of package, the teardown code does not execute.

Simple example:

@pytest.fixture(scope="package")
def example():
   setup_code()
   yield something
   teardown_code()

For this example, "teardown_code()" is never executed for me.

[nicoddemus]

Hi @hayleyday,

Thanks for reporting it. I could not reproduce it with this example though:

import pytest

@pytest.fixture(scope='package')
def fix():
    print('setup')
    yield 1
    print('teardown')

def test(fix):
    assert fix == 1

λ pytest -s -q .tmp\test_pkg_fix.py
setup
.teardown

1 passed in 0.01 seconds

Can you please provide a reproducible example?

[hayleyday]

@nicoddemus It appears that the issue I reported is invalid and that this is not the actual issue I am experiencing. My apologies for that. I might need some clarification on the intent/design of the package scope. Here is an explanation of the issue I am experiencing:

If I have multiple packages in my full overall test package, say test_foo; test_bar; test_baz, each with their own conftest.py and test modules, the tests execute in this order when I run the full overall test package:

1. test_bar package - setup code, asserts for bar modules
2. test_baz package - setup code, asserts for baz modules
3. test_foo package - setup code, asserts for foo modules
4. foo package teardown code
5. baz package teardown code
6. bar package teardown code

See attached screenshot. Please advise if this is intended behavior. Thank you very much for your time!

[nicoddemus]

Hi @hayleyday sorry for the delay.

Hmm I would expect the tear down of the packages to occur right after the last test of the module inside of the package to finish. It is late now and I need to go to bed, but I will ping @jonozzz in case he has any comments. 👍

[akumarpatel]

@nicoddemus It appears that the issue I reported is invalid and that this is not the actual issue I am experiencing. My apologies for that. I might need some clarification on the intent/design of the package scope. Here is an explanation of the issue I am experiencing:

If I have multiple packages in my full overall test package, say test_foo; test_bar; test_baz, each with their own conftest.py and test modules, the tests execute in this order when I run the full overall test package:

1. test_bar package - setup code, asserts for bar modules
2. test_baz package - setup code, asserts for baz modules
3. test_foo package - setup code, asserts for foo modules
4. foo package teardown code
5. baz package teardown code
6. bar package teardown code

See attached screenshot. Please advise if this is intended behavior. Thank you very much for your time!

@hayleyday Is your issue been resolved ? because I facing the same issue with teardown of package scope fixtures with pytest version 3.9.0.

[hayleyday]

@akumarpatel Sorry for the delay. My issue has been resolved... However, I have only been using pytest 3.7.3. If I find the time, I will upgrade to 3.9.0 and see if that changes anything for me.

[aliaksandr-klimovich]

I faced same issue in pytest v7.2.0.
The teardown of the fixtures with the "package" scope is executed at the end of all tests.