Fix spinach tests
This commit is contained in:
parent
6662f034be
commit
657ac981ac
|
@ -84,7 +84,7 @@
|
||||||
break;
|
break;
|
||||||
case 'projects:merge_requests:index':
|
case 'projects:merge_requests:index':
|
||||||
case 'projects:issues:index':
|
case 'projects:issues:index':
|
||||||
if(gl.FilteredSearchManager) {
|
if(document.querySelector('.filtered-search') && gl.FilteredSearchManager) {
|
||||||
new gl.FilteredSearchManager();
|
new gl.FilteredSearchManager();
|
||||||
}
|
}
|
||||||
Issuable.init();
|
Issuable.init();
|
||||||
|
|
|
@ -1,28 +0,0 @@
|
||||||
@project_issues
|
|
||||||
Feature: Project Issues Filter Labels
|
|
||||||
Background:
|
|
||||||
Given I sign in as a user
|
|
||||||
And I own project "Shop"
|
|
||||||
And project "Shop" has labels: "bug", "feature", "enhancement"
|
|
||||||
And project "Shop" has issue "Bugfix1" with labels: "bug", "feature"
|
|
||||||
And project "Shop" has issue "Bugfix2" with labels: "bug", "enhancement"
|
|
||||||
And project "Shop" has issue "Feature1" with labels: "feature"
|
|
||||||
Given I visit project "Shop" issues page
|
|
||||||
|
|
||||||
@javascript
|
|
||||||
Scenario: I filter by one label
|
|
||||||
Given I click link "bug"
|
|
||||||
And I click "dropdown close button"
|
|
||||||
Then I should see "Bugfix1" in issues list
|
|
||||||
And I should see "Bugfix2" in issues list
|
|
||||||
And I should not see "Feature1" in issues list
|
|
||||||
|
|
||||||
# TODO: make labels filter works according to this scanario
|
|
||||||
# right now it looks for label 1 OR label 2. Old behaviour (this test) was
|
|
||||||
# all issues that have both label 1 AND label 2
|
|
||||||
#Scenario: I filter by two labels
|
|
||||||
#Given I click link "bug"
|
|
||||||
#And I click link "feature"
|
|
||||||
#Then I should see "Bugfix1" in issues list
|
|
||||||
#And I should not see "Bugfix2" in issues list
|
|
||||||
#And I should not see "Feature1" in issues list
|
|
|
@ -26,12 +26,6 @@ Feature: Project Issues
|
||||||
Given I click link "Release 0.4"
|
Given I click link "Release 0.4"
|
||||||
Then I should see issue "Release 0.4"
|
Then I should see issue "Release 0.4"
|
||||||
|
|
||||||
@javascript
|
|
||||||
Scenario: I filter by author
|
|
||||||
Given I add a user to project "Shop"
|
|
||||||
And I click "author" dropdown
|
|
||||||
Then I see current user as the first user
|
|
||||||
|
|
||||||
Scenario: I submit new unassigned issue
|
Scenario: I submit new unassigned issue
|
||||||
Given I click link "New Issue"
|
Given I click link "New Issue"
|
||||||
And I submit new issue "500 error on profile"
|
And I submit new issue "500 error on profile"
|
||||||
|
@ -84,56 +78,6 @@ Feature: Project Issues
|
||||||
And I sort the list by "Least popular"
|
And I sort the list by "Least popular"
|
||||||
Then The list should be sorted by "Least popular"
|
Then The list should be sorted by "Least popular"
|
||||||
|
|
||||||
@javascript
|
|
||||||
Scenario: I search issue
|
|
||||||
Given I fill in issue search with "Re"
|
|
||||||
Then I should see "Release 0.4" in issues
|
|
||||||
And I should not see "Release 0.3" in issues
|
|
||||||
And I should not see "Tweet control" in issues
|
|
||||||
|
|
||||||
@javascript
|
|
||||||
Scenario: I search issue that not exist
|
|
||||||
Given I fill in issue search with "Bu"
|
|
||||||
Then I should not see "Release 0.4" in issues
|
|
||||||
And I should not see "Release 0.3" in issues
|
|
||||||
|
|
||||||
@javascript
|
|
||||||
Scenario: I search all issues
|
|
||||||
Given I click link "All"
|
|
||||||
And I fill in issue search with ".3"
|
|
||||||
Then I should see "Release 0.3" in issues
|
|
||||||
And I should not see "Release 0.4" in issues
|
|
||||||
|
|
||||||
@javascript
|
|
||||||
Scenario: Search issues when search string exactly matches issue description
|
|
||||||
Given project 'Shop' has issue 'Bugfix1' with description: 'Description for issue1'
|
|
||||||
And I fill in issue search with 'Description for issue1'
|
|
||||||
Then I should see 'Bugfix1' in issues
|
|
||||||
And I should not see "Release 0.4" in issues
|
|
||||||
And I should not see "Release 0.3" in issues
|
|
||||||
And I should not see "Tweet control" in issues
|
|
||||||
|
|
||||||
@javascript
|
|
||||||
Scenario: Search issues when search string partially matches issue description
|
|
||||||
Given project 'Shop' has issue 'Bugfix1' with description: 'Description for issue1'
|
|
||||||
And project 'Shop' has issue 'Feature1' with description: 'Feature submitted for issue1'
|
|
||||||
And I fill in issue search with 'issue1'
|
|
||||||
Then I should see 'Feature1' in issues
|
|
||||||
Then I should see 'Bugfix1' in issues
|
|
||||||
And I should not see "Release 0.4" in issues
|
|
||||||
And I should not see "Release 0.3" in issues
|
|
||||||
And I should not see "Tweet control" in issues
|
|
||||||
|
|
||||||
@javascript
|
|
||||||
Scenario: Search issues when search string matches no issue description
|
|
||||||
Given project 'Shop' has issue 'Bugfix1' with description: 'Description for issue1'
|
|
||||||
And I fill in issue search with 'Rock and roll'
|
|
||||||
Then I should not see 'Bugfix1' in issues
|
|
||||||
And I should not see "Release 0.4" in issues
|
|
||||||
And I should not see "Release 0.3" in issues
|
|
||||||
And I should not see "Tweet control" in issues
|
|
||||||
|
|
||||||
|
|
||||||
# Markdown
|
# Markdown
|
||||||
|
|
||||||
Scenario: Headers inside the description should have ids generated for them.
|
Scenario: Headers inside the description should have ids generated for them.
|
||||||
|
|
Loading…
Reference in New Issue