Hi Jack I can explain this a bit. RSpec itself has no inbuilt support for browser testing at all.
Feature specs are a configuration of Capybara on top of RSpec that is part of `rspec-rails` a “convention other configuration” from when that was the recommended way to go with testing full stack setups within Rails. System specs are Rails own replacement for this previous “convention”. If you are using system specs I would probably replace feature specs with them. Hope that helps! Jon ---------------- [email protected] https://jonrowe.co.uk On 3 December 2020 at 00:55, Jack Royal-Gordon wrote: > I am still wondering why the decision was made not to add this RSpec > functionality to feature specs — I think that there is no other difference > between feature specs and system specs, although looking at the code for > SystemExampleGroup vs. FeatureExampleGroup there seems quite a significant > difference. Perhaps it’s because it’s driving Rails’ > ActionDispatch::Integration instead of being RSpec-only. > > I guess the difference is that your approach is independent of RSpec, whereas > mine uses RSpec. I could not get your approach to fire up headless Chrome > (although I didn’t try your exact code, just code that should have the same > effect (some options are different, but “headless” is still there. -- You received this message because you are subscribed to the Google Groups "rspec" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rspec/dejalu-217-5bc1a821-9fb1-489c-9633-136b1157c4dc%40jonrowe.co.uk.
