You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: days/10-12-pytest/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ On the topic of more complex code, one thing I did not cover are `pytest` fixtur
34
34
35
35
> The purpose of test fixtures is to provide a fixed baseline upon which tests can reliably and repeatedly execute. pytest fixtures offer dramatic improvements over the classic xUnit style of setup/teardown functions - [pytest fixtures: explicit, modular, scalable](https://docs.pytest.org/en/latest/fixture.html)
36
36
37
-
A typical example is a database app that needs to setup and tear down its state before each test. Read through [the docs](https://docs.pytest.org/en/latest/fixture.html) and/or this article: [`pytest` fixtures easy example](http://pythontesting.net/framework/pytest/pytest-fixtures-easy-example/). Then try to find a use case for the `pytest.fixture`decorator. For example, I used it [for this small DB app](https://realpython.com/blog/python/building-a-simple-web-app-with-bottle-sqlalchemy-twitter-api/#add-tests-with-pytest) (code [here](https://github.com/pybites/pytip/blob/master/tests/test_tips.py)).
37
+
A typical example is a database app that needs to setup and tear down its state before each test. Today try to come up with a use case to use `@pytest.fixture`after checking out our article: [All You Need to Know to Start Using Fixtures in Your pytest Code](https://pybit.es/pytest-fixtures.html).
0 commit comments