Repeated RSpec assertions can be extracted into custom matchers, but some cases are better served by private helper methods when reuse would be too awkward.

Strict loading in index actions catches N+1 queries when views touch unpreloaded associations, causing test failures instead of hidden database hits.

Remote Chrome debugging in Docker is awkward when integration tests need a browser you can inspect. SSH port forwarding can expose a local chromedriver inside the test container.

RubyMine test navigation depends on marking test folders as Test Sources Root; remapping CTRL + ALT + SHIFT + c can copy repository-relative paths like spec/foo_spec.rb instead of foo_spec.rb.

Chromedriver on Linux often falls out of sync with Chrome, causing test failures. Official downloads, geordi chromedriver-update, or package-based installs can keep the driver current.

Unlogged PostgreSQL tables can speed up Rails test suites by skipping the write-ahead log, but they raise crash-related data loss risk and stay unsuitable for production.

Conditional VCR cassette re-recording for RSpec specs avoids manual YAML deletion while iterating on failing tests.

Fresh Chrome installs in Europe can trigger a search-engine choice popup that breaks Cucumber tests; --disable-search-engine-choice-screen disables it.

Use git worktree to keep multiple working trees on one repository, so you can test, compare versions, and switch branches without disturbing current work.

Cookie-dependent behavior in Rails specs is hard to test outside controller specs, especially signed and encrypted values. ActionDispatch::Cookies::CookieJar provides isolated access in request and helper specs.

Capybara multi-session tests support simultaneous users in browser-based chat flows, but session-aware authentication state is needed to avoid conflicts.

RSpec file loading order affects test stability only when examples depend on global state; version defaults differ between alphabetical, disk, and random execution.

Flaky waitFor tests can fail when Jasmine expectations do not throw, preventing retries. throwUnless and throwUnlessAsync turn failed checks into exceptions for reliable waiting.

Rails log files rotate automatically around 100 MB, and config.log_file_size lets you cap growth and keep logs manageable in development, test, or production.

Capybara/Selenium tests involve a test process, a server thread and a browser process, so blocking, stale time, and uncommitted transactions can cause seemingly impossible failures.

Chromedriver logging helps diagnose Selenium Chrome test failures by recording driver activity to a file or terminal. Service configuration or a manually started driver can enable verbose output.

Map readable Cucumber locators to CSS via BEM classes or aria-label, so integration tests target page elements without manual selector rules.

Reliable file-download testing in Capybara, including filename, content type, disposition, and text inspection across Selenium and Rack::Test without leaving the page.

Run only edited or newly added RSpec files in the current branch by diffing against master, which speeds feedback on focused test changes.

Chrome password leak detection can interrupt Selenium runs with breach warnings on weak or reused credentials. Disabling profile.password_manager_leak_detection suppresses the dialog in automated tests.

Parallel test runs can exceed Redis’s default 16 databases on multi-core machines, causing ERR DB index is out of range; increasing the database limit resolves it.

Set browser cookies in Cucumber feature tests when you need to simulate visitors with existing cookie data across the full application stack.

Transactional test fixtures can suppress after_commit callbacks in Rails, preventing email jobs and other post-save work from running. Rails 5 fixes this; older versions can use test_after_commit.

Capybara 3 no longer squishes whitespace when matching text across elements, so tests that relied on rendered text comparison can fail unless normalization is enabled.