Leo Hemsted 44a8526807 use pytest.mark.usefixtures instead of funcargs ...

when you invoke the fixture `sample_user`, it does two things: it
creates the user in the database, but also returns the user, a useful
object that you may want to manipulate or reference in your test.

however, when you invoke the fixture `notify_db_session`, it doesn't
do anything - rather, it *promises* to clear up the database tables
at the end of the test run.

because we have no need of the notify_db_session object in our tests
(indeed, for a long time this fixture just returned `None`), using
`pytest.mark.usefixtures('notify_db_session')` brings attention to the
fact that this is a side-effect fixture rather than a data setup
fixture. Functionally it is identical to passing as a parameter

2017-01-10 15:04:28 +00:00

..

app

use pytest.mark.usefixtures instead of funcargs

2017-01-10 15:04:28 +00:00

__init__.py

add test that if we have an exception, nothing is committed

2016-11-11 14:40:25 +00:00

conftest.py

dont let user update prov details version, and refactor tests

2016-12-19 17:13:10 +00:00