kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Remove commented tests since nobody is going to fix them

Browse source
This commit is contained in:
Dmitriy Zaporozhets 2013-09-11 22:50:08 +03:00
parent 13fec18ac9
commit 7bf8d22f17
3 changed files with 0 additions and 71 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
features/project/forked_merge_requests.feature
View file

@ -4,15 +4,6 @@ Feature: Project Forked Merge Requests
And I am a member of project "Shop"
And I have a project forked off of "Shop" called "Forked Shop"
# TODO: fix
#@javascript
#Scenario: I can visit the target projects commit for a forked merge request
#Given I visit project "Forked Shop" merge requests page
#And I click link "New Merge Request"
#And I fill out a "Merge Request On Forked Project" merge request
#And I follow the target commit link
#Then I should see the commit under the forked from project
@javascript
Scenario: I submit new unassigned merge request to a forked project
Given I visit project "Forked Shop" merge requests page

17
features/project/issues/issues.feature
View file

@ -54,20 +54,3 @@ Feature: Project Issues
And I fill in issue search with "0.3"
Then I should see "Release 0.3" in issues
And I should not see "Release 0.4" in issues
# Disable this two cause of random failing
# TODO: fix after v4.0 released
#@javascript
#Scenario: I create Issue with pre-selected milestone
#Given project "Shop" has milestone "v2.2"
#And project "Shop" has milestone "v3.0"
#And I visit project "Shop" issues page
#When I select milestone "v3.0"
#And I click link "New Issue"
#Then I should see selected milestone with title "v3.0"
#@javascript
#Scenario: I create Issue with pre-selected assignee
#When I select first assignee from "Shop" project
#And I click link "New Issue"
#Then I should see first assignee from "Shop" as selected assignee

45
spec/features/notes_on_merge_requests_spec.rb
View file

@ -206,17 +206,6 @@ describe "On a merge request diff", js: true, focus: true do
find(".js-note-preview-button").trigger("click")
end
end
# TODO: fix
#it 'should check if previews were rendered separately' do
#within("tr[id='4735dfc552ad7bf15ca468adc3cad9d05b624490_185_185'] + .js-temp-notes-holder") do
#should have_css(".js-note-preview", text: "One comment on line 185")
#end
#within("tr[id='342e16cbbd482ac2047dc679b2749d248cc1428f_18_17'] + .js-temp-notes-holder") do
#should have_css(".js-note-preview", text: "Another comment on line 17")
#end
#end
end
describe "posting a note" do
@ -239,42 +228,8 @@ describe "On a merge request diff", js: true, focus: true do
should have_css(".notes_holder .note", count: 1)
should have_link("Reply")
end
# TODO: fix
#it "should remove last note of a discussion" do
# within("tr[id='342e16cbbd482ac2047dc679b2749d248cc1428f_18_17'] + .notes-holder") do
# find(".js-note-delete").click
# end
# should_not have_css(".note_holder")
#end
end
end
# TODO: fix
#describe "when replying to a note" do
#before do
## create first note
# find('a[data-line-code="4735dfc552ad7bf15ca468adc3cad9d05b624490_184_184"]').click
# within(".js-temp-notes-holder") do
# fill_in "note[note]", with: "One comment on line 184"
# click_button("Add Comment")
#end
# within(".js-temp-notes-holder") do
# find(".js-discussion-reply-button").click
# fill_in "note[note]", with: "An additional comment in reply"
# click_button("Add Comment")
# end
#end
#it 'should be inserted and form removed from reply' do
# should have_content("An additional comment in reply")
# within(".notes_holder") { should have_css(".note", count: 2) }
# within(".notes_holder") { should have_no_css("form") }
# within(".notes_holder") { should have_link("Reply") }
# end
#end
end
describe "On merge request discussion", js: true do