rubyforgood
[FEAT]: Utilize transactional fixtures in test suite so that they are faster
Is there an existing request for this feature?
- [X] I have searched the existing issues
Is there a pain point in the app driving this feature request?
Running the test suites has been notoriously slow since we've gotten rid of transactional fixtures. It was changed in https://github.com/rubyforgood/human-essentials/pull/2084 due to having two databases that didn't play nicely with transactional fixtures and thus lead to failed specs.
Now that we have merged the two databases into a single one, it is time to bring back transactional fixtures so that our tests aren't bogged down by actually having to create new records and clean them up.
Desired Behavior
The use_transactional_fixtures is set to true and we notice a speed increase in our testing suite.
Criteria for Completion
- [ ] use_transactional_fixtures is set to true
- [ ] Specs still continue to pass.
Anything else?
I would check out the changes in https://github.com/rubyforgood/human-essentials/pull/2084 as a reference point for figuring out how to get back to using transactional fixtures.
Code of Conduct
- [X] I've read the Code of Conduct and understand my responsibilities as a member of the Ruby for Good community
