gitlab-org--gitlab-foss/spec/features/gitlab_flavored_markdown_spec.rb

139 lines
4.2 KiB
Ruby
Raw Normal View History

require 'spec_helper'
describe "GitLab Flavored Markdown", feature: true do
let(:project) { create(:project) }
let(:issue) { create(:issue, project: project) }
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(:fred) 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
u = create(:user, name: "fred")
project.team << [u, :master]
u
end
before do
2015-05-21 17:49:06 -04:00
allow_any_instance_of(Commit).to receive(:title).
and_return("fix #{issue.to_reference}\n\nask #{fred.to_reference} for details")
end
2012-09-14 18:00:59 -04:00
2015-04-21 09:13:40 -04:00
let(:commit) { project.commit }
before do
login_as :user
2013-01-04 11:50:31 -05:00
project.team << [@user, :developer]
end
describe "for commits" do
it "renders title in commits#index" do
visit namespace_project_commits_path(project.namespace, project, 'master', limit: 1)
2015-05-21 16:35:15 -04:00
expect(page).to have_link(issue.to_reference)
end
it "renders title in commits#show" do
visit namespace_project_commit_path(project.namespace, project, commit)
2015-05-21 16:35:15 -04:00
expect(page).to have_link(issue.to_reference)
end
it "renders description in commits#show" do
visit namespace_project_commit_path(project.namespace, project, commit)
2015-05-21 16:35:15 -04:00
expect(page).to have_link(fred.to_reference)
end
it "renders title in repositories#branches" do
visit namespace_project_branches_path(project.namespace, project)
2015-05-21 16:35:15 -04:00
expect(page).to have_link(issue.to_reference)
end
end
2017-04-05 21:13:06 -04:00
describe "for issues", feature: true, js: true do
include WaitForVueResource
before do
@other_issue = create(:issue,
author: @user,
assignee: @user,
project: project)
@issue = create(:issue,
author: @user,
assignee: @user,
project: project,
2015-05-21 16:35:15 -04:00
title: "fix #{@other_issue.to_reference}",
description: "ask #{fred.to_reference} for details")
end
it "renders subject in issues#index" do
visit namespace_project_issues_path(project.namespace, project)
2015-05-21 16:35:15 -04:00
expect(page).to have_link(@other_issue.to_reference)
end
it "renders subject in issues#show" do
visit namespace_project_issue_path(project.namespace, project, @issue)
2015-05-21 16:35:15 -04:00
expect(page).to have_link(@other_issue.to_reference)
end
it "renders details in issues#show" do
visit namespace_project_issue_path(project.namespace, project, @issue)
expect(page).to have_link(fred.to_reference)
end
2017-04-05 21:13:06 -04:00
it "renders updated subject once edited somewhere else in issues#show" do
visit namespace_project_issue_path(project.namespace, project, @issue)
@issue.update(title: "fix #{@other_issue.to_reference} and update")
wait_for_vue_resource
expect(page).to have_text("fix #{@other_issue.to_reference} and update")
end
end
describe "for merge requests" do
before do
2015-05-21 16:35:15 -04:00
@merge_request = create(:merge_request, source_project: project, target_project: project, title: "fix #{issue.to_reference}")
end
it "renders title in merge_requests#index" do
visit namespace_project_merge_requests_path(project.namespace, project)
2015-05-21 16:35:15 -04:00
expect(page).to have_link(issue.to_reference)
end
it "renders title in merge_requests#show" do
visit namespace_project_merge_request_path(project.namespace, project, @merge_request)
2015-05-21 16:35:15 -04:00
expect(page).to have_link(issue.to_reference)
end
end
describe "for milestones" do
before do
@milestone = create(:milestone,
project: project,
2015-05-21 16:35:15 -04:00
title: "fix #{issue.to_reference}",
description: "ask #{fred.to_reference} for details")
end
it "renders title in milestones#index" do
visit namespace_project_milestones_path(project.namespace, project)
2015-05-21 16:35:15 -04:00
expect(page).to have_link(issue.to_reference)
end
it "renders title in milestones#show" do
visit namespace_project_milestone_path(project.namespace, project, @milestone)
2015-05-21 16:35:15 -04:00
expect(page).to have_link(issue.to_reference)
end
it "renders description in milestones#show" do
visit namespace_project_milestone_path(project.namespace, project, @milestone)
2015-05-21 16:35:15 -04:00
expect(page).to have_link(fred.to_reference)
end
end
end