summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYorick Peterse <yorickpeterse@gmail.com>2016-03-21 11:40:13 +0100
committerYorick Peterse <yorickpeterse@gmail.com>2016-03-21 11:40:13 +0100
commit75aaf91cb1d08c4350e2881b18118faf30e1f310 (patch)
tree73d68e72d9061a0bd9ea8166e2cea2949c7a4476
parentfc5ff7af61e14b89b67febf4167a03a0133e55ed (diff)
downloadgitlab-ce-issues-show-performance.tar.gz
Create SSH keys for SSH clone Spinach testsissues-show-performance
These tests would check if the "This project is empty" banner would contain SSH clone URLs. Oddly enough this should have never passed (as far as I can tell) as SSH clone URLs in this banner are _only_ displayed if the current user has at least 1 SSH key attached. Since the tests never seem to create any they never should have passed, yet somehow they did. To solve this the Spinach tests in question now ensure at least 1 SSH key is present.
-rw-r--r--features/project/issues/issues.feature1
-rw-r--r--features/steps/project/issues/issues.rb1
2 files changed, 2 insertions, 0 deletions
diff --git a/features/project/issues/issues.feature b/features/project/issues/issues.feature
index ff21c7d1b83..de7e2b37725 100644
--- a/features/project/issues/issues.feature
+++ b/features/project/issues/issues.feature
@@ -160,6 +160,7 @@ Feature: Project Issues
Scenario: Issues on empty project
Given empty project "Empty Project"
+ And I have an ssh key
When I visit empty project page
And I see empty project details with ssh clone info
When I visit empty project's issues page
diff --git a/features/steps/project/issues/issues.rb b/features/steps/project/issues/issues.rb
index 307d32fd610..aff5ca676be 100644
--- a/features/steps/project/issues/issues.rb
+++ b/features/steps/project/issues/issues.rb
@@ -5,6 +5,7 @@ class Spinach::Features::ProjectIssues < Spinach::FeatureSteps
include SharedNote
include SharedPaths
include SharedMarkdown
+ include SharedUser
step 'I should see "Release 0.4" in issues' do
expect(page).to have_content "Release 0.4"