gitlab-org--gitlab-foss/features/steps/dashboard/merge_requests.rb

75 lines
2 KiB
Ruby
Raw Normal View History

class DashboardMergeRequests < Spinach::FeatureSteps
2012-09-10 11:35:03 -04:00
include SharedAuthentication
include SharedPaths
step 'I should see merge requests assigned to me' do
should_see(assigned_merge_request)
should_not_see(authored_merge_request)
should_not_see(other_merge_request)
end
step 'I should see merge requests authored by me' do
should_see(authored_merge_request)
should_not_see(assigned_merge_request)
should_not_see(other_merge_request)
end
step 'I should see all merge requests' do
should_see(authored_merge_request)
should_see(assigned_merge_request)
should_see(other_merge_request)
end
step 'I have authored merge requests' do
authored_merge_request
end
step 'I have assigned merge requests' do
assigned_merge_request
end
step 'I have other merge requests' do
other_merge_request
end
step 'I click "Authored by me" link' do
within ".scope-filter" do
click_link 'Created by me'
end
end
step 'I click "All" link' do
within ".scope-filter" do
click_link "Everyone's"
end
end
def should_see(merge_request)
page.should have_content(merge_request.title[0..10])
end
def should_not_see(merge_request)
page.should_not have_content(merge_request.title[0..10])
end
def assigned_merge_request
@assigned_merge_request ||= create :merge_request, assignee: current_user, target_project: project, source_project: project
end
def authored_merge_request
@authored_merge_request ||= create :merge_request, source_branch: 'simple_merge_request', author: current_user, target_project: project, source_project: project
end
def other_merge_request
@other_merge_request ||= create :merge_request, source_branch: '2_3_notes_fix', target_project: project, source_project: project
end
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
def project
@project ||= begin
project =create :project
project.team << [current_user, :master]
project
end
end
end