Skip to content

Commit 5ceca8b

Browse files
committed
update readme
1 parent 80e2f2e commit 5ceca8b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

days/10-12-pytest/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ On the topic of more complex code, one thing I did not cover are `pytest` fixtur
3434

3535
> 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)
3636
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).
3838

3939
Ready to become a `pytest` ninja? You can do it!
4040

0 commit comments

Comments
 (0)