gitlab-org--gitlab-foss/spec/mailers/notify_spec.rb

419 lines
12 KiB
Ruby
Raw Normal View History

require 'spec_helper'
describe Notify do
include EmailSpec::Helpers
include EmailSpec::Matchers
let(:recipient) { create(:user, email: 'recipient@example.com') }
let(:project) { create(:project_with_code) }
2012-05-14 18:03:30 -04:00
shared_examples 'a multiple recipients email' do
it 'is sent to the given recipient' do
should deliver_to recipient.email
end
end
describe 'for new users, the email' do
let(:example_site_path) { root_path }
2013-06-14 05:58:12 -04:00
let(:new_user) { create(:user, email: 'newguy@example.com', created_by_id: 1) }
subject { Notify.new_user_email(new_user.id, new_user.password) }
it 'is sent to the new user' do
should deliver_to new_user.email
end
it 'has the correct subject' do
2012-09-06 04:40:16 -04:00
should have_subject /^gitlab \| Account was created for you$/i
end
it 'contains the new user\'s login name' do
should have_body_text /#{new_user.email}/
end
it 'contains the new user\'s password' do
2013-06-14 05:58:12 -04:00
should have_body_text /password/
end
it 'includes a link to the site' do
should have_body_text /#{example_site_path}/
end
end
2012-11-06 08:30:48 -05:00
describe 'for users that signed up, the email' do
let(:example_site_path) { root_path }
let(:new_user) { create(:user, email: 'newguy@example.com', password: "securePassword") }
subject { Notify.new_user_email(new_user.id, new_user.password) }
it 'is sent to the new user' do
should deliver_to new_user.email
end
it 'has the correct subject' do
should have_subject /^gitlab \| Account was created for you$/i
end
it 'contains the new user\'s login name' do
should have_body_text /#{new_user.email}/
end
it 'should not contain the new user\'s password' do
2013-06-14 05:58:12 -04:00
should_not have_body_text /password/
2012-11-06 08:30:48 -05:00
end
it 'includes a link to the site' do
should have_body_text /#{example_site_path}/
end
end
describe 'user added ssh key' do
let(:key) { create(:personal_key) }
subject { Notify.new_ssh_key_email(key.id) }
it 'is sent to the new user' do
should deliver_to key.user.email
end
it 'has the correct subject' do
should have_subject /^gitlab \| SSH key was added to your account$/i
end
it 'contains the new ssh key title' do
should have_body_text /#{key.title}/
end
it 'includes a link to ssh keys page' do
2013-06-24 12:24:27 -04:00
should have_body_text /#{profile_keys_path}/
end
end
2012-05-14 18:03:30 -04:00
context 'for a project' do
describe 'items that are assignable, the email' do
let(:assignee) { create(:user, email: 'assignee@example.com') }
let(:previous_assignee) { create(:user, name: 'Previous Assignee') }
2012-05-14 18:03:30 -04:00
shared_examples 'an assignee email' do
it 'is sent to the assignee' do
should deliver_to assignee.email
end
end
2012-05-14 18:03:30 -04:00
context 'for issues' do
let(:issue) { create(:issue, assignee: assignee, project: project ) }
2012-05-14 18:03:30 -04:00
describe 'that are new' do
subject { Notify.new_issue_email(issue.assignee_id, issue.id) }
2012-05-14 18:03:30 -04:00
it_behaves_like 'an assignee email'
2012-05-14 18:03:30 -04:00
it 'has the correct subject' do
should have_subject /#{project.name} \| New issue ##{issue.iid} \| #{issue.title}/
2012-05-14 18:03:30 -04:00
end
2012-05-14 18:03:30 -04:00
it 'contains a link to the new issue' do
should have_body_text /#{project_issue_path project, issue}/
2012-05-14 18:03:30 -04:00
end
end
2012-05-14 18:03:30 -04:00
describe 'that have been reassigned' do
before(:each) { issue.stub(:assignee_id_was).and_return(previous_assignee.id) }
subject { Notify.reassigned_issue_email(recipient.id, issue.id, previous_assignee.id) }
2012-05-14 18:03:30 -04:00
it_behaves_like 'a multiple recipients email'
it 'has the correct subject' do
should have_subject /Changed issue ##{issue.iid} \| #{issue.title}/
2012-05-14 18:03:30 -04:00
end
it 'contains the name of the previous assignee' do
should have_body_text /#{previous_assignee.name}/
2012-05-14 18:03:30 -04:00
end
it 'contains the name of the new assignee' do
should have_body_text /#{assignee.name}/
end
it 'contains a link to the issue' do
should have_body_text /#{project_issue_path project, issue}/
2012-05-14 18:03:30 -04:00
end
end
2012-08-29 02:49:39 -04:00
describe 'status changed' do
let(:current_user) { create(:user, email: "current@email.com") }
2012-08-29 02:49:39 -04:00
let(:status) { 'closed' }
subject { Notify.issue_status_changed_email(recipient.id, issue.id, status, current_user) }
2012-08-29 02:49:39 -04:00
it 'has the correct subject' do
should have_subject /Changed issue ##{issue.iid} \| #{issue.title}/i
2012-08-29 02:49:39 -04:00
end
it 'contains the new status' do
should have_body_text /#{status}/i
end
it 'contains the user name' do
should have_body_text /#{current_user.name}/i
end
it 'contains a link to the issue' do
should have_body_text /#{project_issue_path project, issue}/
end
end
2012-05-14 18:03:30 -04:00
end
context 'for merge requests' do
Merge Request on forked projects The good: - You can do a merge request for a forked commit and it will merge properly (i.e. it does work). - Push events take into account merge requests on forked projects - Tests around merge_actions now present, spinach, and other rspec tests - Satellites now clean themselves up rather then recreate The questionable: - Events only know about target projects - Project's merge requests only hold on to MR's where they are the target - All operations performed in the satellite The bad: - Duplication between project's repositories and satellites (e.g. commits_between) (for reference: http://feedback.gitlab.com/forums/176466-general/suggestions/3456722-merge-requests-between-projects-repos) Fixes: Make test repos/satellites only create when needed -Spinach/Rspec now only initialize test directory, and setup stubs (things that are relatively cheap) -project_with_code, source_project_with_code, and target_project_with_code now create/destroy their repos individually -fixed remote removal -How to merge renders properly -Update emails to show project/branches -Edit MR doesn't set target branch -Fix some failures on editing/creating merge requests, added a test -Added back a test around merge request observer -Clean up project_transfer_spec, Remove duplicate enable/disable observers -Ensure satellite lock files are cleaned up, Attempted to add some testing around these as well -Signifant speed ups for tests -Update formatting ordering in notes_on_merge_requests -Remove wiki schema update Fixes for search/search results -Search results was using by_project for a list of projects, updated this to use in_projects -updated search results to reference the correct (target) project -udpated search results to print both sides of the merge request Change-Id: I19407990a0950945cc95d62089cbcc6262dab1a8
2013-04-25 10:15:33 -04:00
let(:merge_request) { create(:merge_request, assignee: assignee, source_project: project, target_project: project) }
2012-05-14 18:03:30 -04:00
describe 'that are new' do
subject { Notify.new_merge_request_email(merge_request.assignee_id, merge_request.id) }
2012-05-14 18:03:30 -04:00
it_behaves_like 'an assignee email'
it 'has the correct subject' do
should have_subject /New merge request ##{merge_request.iid}/
2012-05-14 18:03:30 -04:00
end
it 'contains a link to the new merge request' do
should have_body_text /#{project_merge_request_path(project, merge_request)}/
2012-05-14 18:03:30 -04:00
end
it 'contains the source branch for the merge request' do
should have_body_text /#{merge_request.source_branch}/
end
it 'contains the target branch for the merge request' do
should have_body_text /#{merge_request.target_branch}/
end
end
describe 'that are reassigned' do
before(:each) { merge_request.stub(:assignee_id_was).and_return(previous_assignee.id) }
2012-05-14 18:03:30 -04:00
subject { Notify.reassigned_merge_request_email(recipient.id, merge_request.id, previous_assignee.id) }
2012-05-14 18:03:30 -04:00
it_behaves_like 'a multiple recipients email'
it 'has the correct subject' do
should have_subject /Changed merge request ##{merge_request.iid}/
2012-05-14 18:03:30 -04:00
end
it 'contains the name of the previous assignee' do
should have_body_text /#{previous_assignee.name}/
2012-05-14 18:03:30 -04:00
end
it 'contains the name of the new assignee' do
should have_body_text /#{assignee.name}/
end
it 'contains a link to the merge request' do
should have_body_text /#{project_merge_request_path project, merge_request}/
2012-05-14 18:03:30 -04:00
end
end
end
end
describe 'project was moved' do
let(:project) { create(:project) }
let(:user) { create(:user) }
subject { Notify.project_was_moved_email(project.id, user.id) }
it 'has the correct subject' do
should have_subject /Project was moved/
end
it 'contains name of project' do
should have_body_text /#{project.name_with_namespace}/
end
it 'contains new user role' do
should have_body_text /#{project.ssh_url_to_repo}/
end
end
describe 'project access changed' do
let(:project) { create(:project) }
let(:user) { create(:user) }
let(:users_project) { create(:users_project,
project: project,
user: user) }
subject { Notify.project_access_granted_email(users_project.id) }
it 'has the correct subject' do
should have_subject /Access to project was granted/
end
it 'contains name of project' do
should have_body_text /#{project.name}/
end
it 'contains new user role' do
2013-08-20 08:59:45 -04:00
should have_body_text /#{users_project.human_access}/
end
end
2012-05-14 18:03:30 -04:00
context 'items that are noteable, the email for a note' do
let(:note_author) { create(:user, name: 'author_name') }
let(:note) { create(:note, project: project, author: note_author) }
2012-05-14 18:03:30 -04:00
before :each do
2013-01-15 09:36:35 -05:00
Note.stub(:find).with(note.id).and_return(note)
end
2012-05-14 18:03:30 -04:00
shared_examples 'a note email' do
it 'is sent to the given recipient' do
should deliver_to recipient.email
end
it 'contains the name of the note\'s author' do
should have_body_text /#{note_author.name}/
end
it 'contains the message from the note' do
should have_body_text /#{note.note}/
end
end
describe 'on a project wall' do
2013-03-19 08:39:32 -04:00
let(:note_on_the_wall_path) { project_wall_path(project, anchor: "note_#{note.id}") }
2012-05-14 18:03:30 -04:00
subject { Notify.note_wall_email(recipient.id, note.id) }
2012-05-14 18:03:30 -04:00
it_behaves_like 'a note email'
it 'has the correct subject' do
should have_subject /#{project.name}/
end
it 'contains a link to the wall note' do
should have_body_text /#{note_on_the_wall_path}/
2012-05-14 18:03:30 -04:00
end
end
describe 'on a commit' do
let(:commit) { project.repository.commit }
2013-01-15 09:36:35 -05:00
2012-10-13 10:23:12 -04:00
before(:each) { note.stub(:noteable).and_return(commit) }
2012-05-14 18:03:30 -04:00
2013-02-01 08:37:21 -05:00
subject { Notify.note_commit_email(recipient.id, note.id) }
2012-05-14 18:03:30 -04:00
it_behaves_like 'a note email'
it 'has the correct subject' do
should have_subject /Note for commit #{commit.short_id}/
2012-05-14 18:03:30 -04:00
end
it 'contains a link to the commit' do
should have_body_text commit.short_id
2012-05-14 18:03:30 -04:00
end
end
describe 'on a merge request' do
Merge Request on forked projects The good: - You can do a merge request for a forked commit and it will merge properly (i.e. it does work). - Push events take into account merge requests on forked projects - Tests around merge_actions now present, spinach, and other rspec tests - Satellites now clean themselves up rather then recreate The questionable: - Events only know about target projects - Project's merge requests only hold on to MR's where they are the target - All operations performed in the satellite The bad: - Duplication between project's repositories and satellites (e.g. commits_between) (for reference: http://feedback.gitlab.com/forums/176466-general/suggestions/3456722-merge-requests-between-projects-repos) Fixes: Make test repos/satellites only create when needed -Spinach/Rspec now only initialize test directory, and setup stubs (things that are relatively cheap) -project_with_code, source_project_with_code, and target_project_with_code now create/destroy their repos individually -fixed remote removal -How to merge renders properly -Update emails to show project/branches -Edit MR doesn't set target branch -Fix some failures on editing/creating merge requests, added a test -Added back a test around merge request observer -Clean up project_transfer_spec, Remove duplicate enable/disable observers -Ensure satellite lock files are cleaned up, Attempted to add some testing around these as well -Signifant speed ups for tests -Update formatting ordering in notes_on_merge_requests -Remove wiki schema update Fixes for search/search results -Search results was using by_project for a list of projects, updated this to use in_projects -updated search results to reference the correct (target) project -udpated search results to print both sides of the merge request Change-Id: I19407990a0950945cc95d62089cbcc6262dab1a8
2013-04-25 10:15:33 -04:00
let(:merge_request) { create(:merge_request, source_project: project, target_project: project) }
let(:note_on_merge_request_path) { project_merge_request_path(project, merge_request, anchor: "note_#{note.id}") }
2012-05-14 18:03:30 -04:00
before(:each) { note.stub(:noteable).and_return(merge_request) }
subject { Notify.note_merge_request_email(recipient.id, note.id) }
2012-05-14 18:03:30 -04:00
it_behaves_like 'a note email'
it 'has the correct subject' do
should have_subject /Note for merge request ##{merge_request.iid}/
2012-05-14 18:03:30 -04:00
end
it 'contains a link to the merge request note' do
should have_body_text /#{note_on_merge_request_path}/
2012-05-14 18:03:30 -04:00
end
end
describe 'on an issue' do
let(:issue) { create(:issue, project: project) }
let(:note_on_issue_path) { project_issue_path(project, issue, anchor: "note_#{note.id}") }
2012-05-14 18:03:30 -04:00
before(:each) { note.stub(:noteable).and_return(issue) }
subject { Notify.note_issue_email(recipient.id, note.id) }
2012-05-14 18:03:30 -04:00
it_behaves_like 'a note email'
it 'has the correct subject' do
should have_subject /Note for issue ##{issue.iid}/
2012-05-14 18:03:30 -04:00
end
it 'contains a link to the issue note' do
should have_body_text /#{note_on_issue_path}/
2012-05-14 18:03:30 -04:00
end
end
end
end
describe 'group access changed' do
let(:group) { create(:group) }
let(:user) { create(:user) }
let(:membership) { create(:users_group, group: group, user: user) }
subject { Notify.group_access_granted_email(membership.id) }
it 'has the correct subject' do
should have_subject /Access to group was granted/
end
it 'contains name of project' do
should have_body_text /#{group.name}/
end
it 'contains new user role' do
should have_body_text /#{membership.human_access}/
end
end
describe 'confirmation if email changed' do
let(:example_site_path) { root_path }
let(:user) { create(:user, email: 'old-email@mail.com') }
before do
user.email = "new-email@mail.com"
user.save
end
subject { ActionMailer::Base.deliveries.last }
it 'is sent to the new user' do
should deliver_to 'new-email@mail.com'
end
it 'has the correct subject' do
should have_subject "Confirmation instructions"
end
it 'includes a link to the site' do
should have_body_text /#{example_site_path}/
end
end
describe 'email on push' do
let(:example_site_path) { root_path }
let(:user) { create(:user) }
let(:compare) { Gitlab::Git::Compare.new(project.repository.raw_repository, 'cd5c4bac', 'b1e6a9db') }
subject { Notify.repository_push_email(project.id, 'devs@company.name', user.id, 'master', compare) }
it 'is sent to recipient' do
should deliver_to 'devs@company.name'
end
it 'has the correct subject' do
should have_subject /New push to repository/
end
it 'includes commits list' do
should have_body_text /tree css fixes/
end
it 'includes diffs' do
should have_body_text /Checkout wiki pages for installation information/
end
end
end