92 lines
3.1 KiB
Gherkin
92 lines
3.1 KiB
Gherkin
|
Feature: Project Issues
|
||
|
|
Background:
|
||
|
|
Given I sign in as a user
|
||
|
|
And I own project "Shop"
|
||
|
|
And project "Shop" have "Release 0.4" open issue
|
||
|
|
And project "Shop" have "Tweet control" open issue
|
||
|
|
And project "Shop" have "Release 0.3" closed issue
|
||
|
|
And I visit project "Shop" issues page
|
||
|
|
|
||
|
|
Scenario: I should see open issues
|
||
|
|
Given I should see "Release 0.4" in issues
|
||
|
|
And I should not see "Release 0.3" in issues
|
||
|
|
|
||
|
|
Scenario: I should see closed issues
|
||
|
|
Given I click link "Closed"
|
||
|
|
Then I should see "Release 0.3" in issues
|
||
|
|
And I should not see "Release 0.4" in issues
|
||
|
|
|
||
|
|
Scenario: I should see all issues
|
||
|
|
Given I click link "All"
|
||
|
|
Then I should see "Release 0.3" in issues
|
||
|
|
And I should see "Release 0.4" in issues
|
||
|
|
|
||
|
|
Scenario: I visit issue page
|
||
|
|
Given I click link "Release 0.4"
|
||
|
|
Then I should see issue "Release 0.4"
|
||
|
|
|
||
|
|
Scenario: I submit new unassigned issue
|
||
|
|
Given I click link "New Issue"
|
||
|
|
And I submit new issue "500 error on profile"
|
||
|
|
Then I should see issue "500 error on profile"
|
||
|
|
|
||
|
|
Scenario: I submit new unassigned issue with labels
|
||
|
|
Given project "Shop" has labels: "bug", "feature", "enhancement"
|
||
|
|
And I click link "New Issue"
|
||
|
|
And I submit new issue "500 error on profile" with label 'bug'
|
||
|
|
Then I should see issue "500 error on profile"
|
||
|
|
And I should see label 'bug' with issue
|
||
|
|
|
||
|
|
@javascript
|
||
|
|
Scenario: I comment issue
|
||
|
|
Given I visit issue page "Release 0.4"
|
||
|
|
And I leave a comment like "XML attached"
|
||
|
|
Then I should see comment "XML attached"
|
||
|
|
|
||
|
|
@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
|
||
|
|
|
||
|
|
# Markdown
|
||
|
|
|
||
|
|
Scenario: Headers inside the description should have ids generated for them.
|
||
|
|
Given I visit issue page "Release 0.4"
|
||
|
|
Then Header "Description header" should have correct id and link
|
||
|
|
|
||
|
|
@javascript
|
||
|
|
Scenario: Headers inside comments should not have ids generated for them.
|
||
|
|
Given I visit issue page "Release 0.4"
|
||
|
|
And I leave a comment with a header containing "Comment with a header"
|
||
|
|
Then The comment with the header should not have an ID
|
||
|
|
|
||
|
|
@javascript
|
||
|
|
Scenario: Blocks inside comments should not build relative links
|
||
|
|
Given I visit issue page "Release 0.4"
|
||
|
|
And I leave a comment with code block
|
||
|
|
Then The code block should be unchanged
|
||
|
|
|
||
|
|
Scenario: Issues on empty project
|
||
|
|
Given empty project "Empty Project"
|
||
|
|
When I visit empty project page
|
||
|
|
And I see empty project details with ssh clone info
|
||
|
|
When I visit empty project's issues page
|
||
|
|
Given I click link "New Issue"
|
||
|
|
And I submit new issue "500 error on profile"
|
||
|
|
Then I should see issue "500 error on profile"
|