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: README.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,6 +52,14 @@ The plugin does not provide a default database fixture, as it is designed to ada
52
52
SQLAlchemy topology. You **must** define a global fixture in your `conftest.py` to bind
53
53
`pytest-capquery` to your project's database engine.
54
54
55
+
Quick references:
56
+
57
+
-[Pytest fixture configuring the DB engine & Capquery context](https://github.com/fmartins/pytest-capquery/blob/main/tests/e2e/postgres/conftest.py)
58
+
-[Test sample using the capquery snapshot support](https://github.com/fmartins/pytest-capquery/blob/main/tests/e2e/postgres/test_snapshot.py)
59
+
-[Test asset for documentation and easy review of the DBA](https://github.com/fmartins/pytest-capquery/blob/main/tests/e2e/postgres/__capquery_snapshots__/test_snapshot/test_insert_and_select_snapshot.sql)
60
+
-[Test sample using the super verbose inline SQL](https://github.com/fmartins/pytest-capquery/blob/main/tests/e2e/postgres/test_assert_executed_queries.py)
61
+
62
+
55
63
### 1. Setting Up Your Fixture (`conftest.py`)
56
64
57
65
To intercept queries from your custom engine, use the `CapQueryWrapper` and inject the
0 commit comments