Adds another selector based on subject.

[ZachBeta]

Resolves issue #22

[bcardarella]

Removing the open_email method changes the public API behavior which I don't want to do.

I think instead there needs to be a general search functionality. Something like

search_emails(:to => 'someone', :from => 'someone', :subject => 'string' or /regex/, :body => 'string' or /regex/)

The body search and subject search will always do a search for emails that contain instead of exact match and you can search by any number of criteria. This will always return a collection. Thoughts?

[ZachBeta]

I was trying to make it as open ended a matcher as possible, like capybara's click_link

click_link('id-of-link')
click_link('Link Text')
click_button('Save')
click_on('Link Text') # clicks on either links or buttons
click_on('Button Value')

It's a lot nicer to work with on the front end although it does change the existing api, it shouldn't break the currently existing functionality.

[bcardarella]

Well the gem follows semantic versioning so I cannot break public API without doing a major version bump which I don't want to do.

As for the selector, I see where you're going but the selectors are meant only to work on one aspect of a document. We would want to search against multiple criteria in which selectors don't make sense.

[ZachBeta]

Understood.

What if we open up the api a bit wider

open_email('[email protected]')
open_email_to('[email protected]') # alias to open_email
open_email_with_subject('Subject Line')

I'm not sure I have the time in the immediate future to properly implement a search_emails({})

And the next big version the api can be reformed updated based on community usage.

[bcardarella]

The gem itself is meant to work only an integration environment. To that end the API reflects how one should work with their own email. The #open_email method is meant to switch the context to the user being imitated in the integration test.

Because integration tests are meant to simulate real-world interactions you wouldn't be expected to be able to just search for all emails the app has sent based upon subject.

After thinking of this, I don't think the correct direction is to change anything in the public API. There are methods to hook into if people want to work around it but I don't want to encourage breaking the personas for integration testing.

[ZachBeta]

In our situation a user receives 2 emails from the application and we're only concerned with the path through one of them.

Since there's already a method emails_sent_to(recipient), we'll be using

emails_sent_to(user.email)
current_email = current_emails.find { |email| email.subject == 'Subject Text 1' }
current_email.click_link('Link text 1')

Hopefully this helps anyone else googling for a solution to a similar problem.

Thanks!