clean database after the after block

[afomi]

goal: to eliminate PG deadlock issues when running specs

[saterus]

Can you include a little more context? What is the difference between #append and #append_after? What lead you to believing this fixes the deadlock?

[afomi]

sure thing @saterus. The links below pointed me toward append_after. Alternatively, people recommended using around blocks as well, but I wanted to try this first, since it was the smallest change.

The difference is: append_after Adds block to the back of the list of after blocks in the same scope (:example, :context, or :suite). - I thought this would give it enough time to let the database locks clear.

• truncation in capybara tests results in rspec freezing (while deletion works) DatabaseCleaner/database_cleaner#273 -
• Rspec after hook being called before spec finishs teamcapybara/capybara#1089 (comment)

I saw append_after in this one:

• http://devblog.avdi.org/2012/08/31/configuring-database_cleaner-with-rails-rspec-capybara-and-selenium/

[saterus]

👍

[mikem]

👍