RSpec and Database Transactions: Retry Logic Interoperability

Transactional Isolation and Example Retries

Maintaining test isolation typically involves wrapping RSpec examples in database transactions using around(:each) hooks or integration tools like DatabaseCleaner. This ensures that writes are rolled back after each example to prevent state leakage.

When integrating external retry mechanisms—such as the rspec-retry gem—the execution flow between the retry loop and the transactional wrapper becomes critical. If a write operation occurs and the example fails, the behavior of the database state during the subsequent attempt depends on whether the transaction is rolled back before the retry is triggered.

In environments using non-transactional stores or specific commit behaviors, retrying an example that has already performed a write may lead to uniqueness constraint violations or duplicate records.

• Does the RSpec execution order guarantee that around hooks are fully exited and rolled back before a retry attempt begins?
• How can the state be consistently reset for non-transactional data stores when using example-level retries?