7 Commits (a18954b2c9c8a1b3f2891cff9910b2b96306b7c0)

Author	SHA1	Message	Date
ulferts	1bdd2ab9ae	safe automatic fixes by rubocop (#8994)	4 years ago
ulferts	c383c5821f	Fix/remove cucumber (#8847) ... * replace very last cuke with spec * remove cuke support files * remove cucumber gems * remove traces of cucumber * remove no longer required route * forcefully clear parallel_test features task * attempt removal of binstub * attempt to stabilize spec	4 years ago
Oliver Günther	c3226bf2c0	Reload shared_lets by default	6 years ago
Oliver Günther	9772f9e883	Re-add puma for single-process testing	6 years ago
Oliver Günther	ca7be0b757	Test to revert to thin and DatabaseCleaner	7 years ago
Oliver Günther	5f0c1aad05	Test to revert to thin and DatabaseCleaner	7 years ago
Oliver Günther	5cfe0d017f	Test to revert to thin and DatabaseCleaner	7 years ago
Oliver Günther	2740d85633	Avoid DatabaseCleaner truncation strategy with in-process puma server ... Since Rails 5.1., we can force the application server and capybara to share the same connection, which results in database_cleaner no longer being necessary and resulting in faster tests due to transactions. This will only work with a server that works in single mode (e.g., Puma). We're still using database_cleaner in cucumber however, so we can use it to ensure we run with a clean database (which use_transactional_fixtures does not ensure) by starting it with truncation once. This PR also adds necessary wiring to support `system` tests, however I don't see the immediate benefit there. rspec will continue to support the previous feature specs syntax.	7 years ago
Oliver Günther	4fb23c957b	Restructure spec_helper into rails_helper and support files	8 years ago