Keep database state after failed test

I don’t think the database is cleaned after each test with sqlite3 sandbox, at least maybe I have something misconfigured, because I am clearing the database manually in data_case.ex after each test.

The ecto sandbox works with wrapping everything in a transaction, so data is never durably written to the db in the first place.

yes, I was wondering if there was an easy way to commit the transaction, so that I can inspect the data.

for me it is cleaned if I use the sandbox.

There is no concept of rollback transactions in ecto sqlite3, at least this is what I understood from @warmwaffles .

You could run your tests in iex and use IEx.pry to inspect things.

This is not a mode of working that I use but here are some posts that explains how to start tests with iex and use IEx.pry:

• Debugging · Elixir School
• How to Use IEx.pry in Elixir Tests - Elixir Tutorials

That’s some nice info, but I don’t think it helps. Because nothing in there is about commiting the transaction.

I think the easiest way to do this (for sqlite), if anyone is interested:

1. remove use Module.DataCase from your test
2. add something like @tag :single to the test you want to run
3. run the test with mix test --only single
4. don’t forget to delete the test database after you’re done and add the DataCase again.

The point of using IE.pry is that the transaction is still alive as you can set a breakpoint so you can do whatever inspection you want, check values, even run db queries in the context of the active transaction.

Can you query data that hasn’t been commited by a transaction?
That doesn’t work as far as I know.
Of course you can inspect it via the elixir tools, but not with the database tools.

You could look into setting the sandbox mode to manual before running a failing test. That would skip the whole transaction wrapping. That might change how the test works across multiple processes though, so keep that in mind.