Vladimir Dementyev
Vladimir Dementyev
Have you included this context into multiple test files? If so, the reason could be the opposite: the block within the `.register` method is called once through the whole test...
Hey @gap777! Any updates on the issue?
> have the DB restored after each test that uses it. Not sure I get this one: you mean clean up database after each test/context? Then, I think, you need...
> This only happens during parallel test execution Do you use threads for parallelization (`parallelize(with: :threads)`)? Also, do you parallelize all tests or only some of them? As I see,...
Oh, that's interesting. That means that our [activation code](https://github.com/test-prof/test-prof/blob/5d263198f8d558f60302481bc2b2f1353e116b65/lib/test_prof/recipes/minitest/before_all.rb#L45) is not triggered and data is created outside of transactions. Do you use fixtures or multiple databases or anything else dealing...
> rails is running tests in any order across all assigned tests. As far as I can see, Rails enqueues methods one by one to be executed in the same...
Hey @quorak! Any updates on this?
Closed as stale
Hey! Are you using Minitest? I'm afraid, boot time profiling is not supported in Minitest (and looks like like we miss this information in the docs—my bad). What you can...
Closed as stale