Best way to test in integration/system tests? about passwordless HOT 3 CLOSED

Hi @rickychilcott! Thank you for your example – that looks like it should work just fine.

In integration/system tests I usually try to get as close to the real thing as possible, so that's what I've been doing.

So something like:

it 'show my posts' do
  user = User.create email: '[email protected]'
  sign_in_by_email user
  expect(page).to have_content('My posts')
end

# ...

def sign_in_by_email(authenticatable)
  visit '/sign_in'
  fill_in 'Email', with: authenticatable.email
  click_button '✨ Send magic link'

  visit_magic_link_in last_email.html_part.body
end

def visit_magic_link_in(html)
  visit text.match(%r{https?://.+(/sign_in/[a-z0-9-]+)}i)[1]
end

def last_email
  ActionMailer::Base.deliveries.last
end

You're totally right about BCrypt in test. I'll skip it 👍

from passwordless.

I totally agree that integrations should test the whole flow, but it does seem a bit silly to test/re-test user sign when what the real intent of a test around a feature is to do some action in your app. There are also the speed gains to be had not triggering the email flow and capybara visiting.

I've always thought https://github.com/thoughtbot/clearance#testing did it nicely with their Backdoor middleware, and I'd be willing to try a PR to get something like this if you think it's worth it.

I think I see a fairly clear way of doing it.

from passwordless.

I like that approach. I wouldn't mind including something like that – a PR would be very welcome! Let me know if you hit any road bumps.

from passwordless.