Commit e6e41478 authored by Lisanne Fellinger's avatar Lisanne Fellinger

Rewritten spinach git_blame tests to rspec feature tests

Fixing rubocop violations

Relocated git_blame spec and fixed styling issue

Rewritten spinach git_blame tests to rspec feature tests

Fixing rubocop violations

Relocated git_blame spec and fixed styling issue

Rewritten spinach git_blame tests to rspec feature tests

Fixing rubocop violations

Rewritten spinach git_blame tests to rspec feature tests

Fixing rubocop violations

Rewritten spinach git_blame tests to rspec feature tests

Fixing rubocop violations

Relocated git_blame spec and fixed styling issue
parent c392b0cc
---
title: Rewrite git blame spinach feature tests to rspec feature tests
merge_request: 7197
author: Lisanne Fellinger
Feature: Project Source Git Blame
Background:
Given I sign in as a user
And I own project "Shop"
Given I visit project source page
Scenario: I blame file
Given I click on ".gitignore" file in repo
And I click Blame button
Then I should see git file blame
class Spinach::Features::ProjectSourceGitBlame < Spinach::FeatureSteps require 'spec_helper'
include SharedAuthentication
include SharedProject
include SharedPaths
step 'I click on ".gitignore" file in repo' do feature 'user checks git blame', feature: true do
click_link ".gitignore" let(:project) { create(:project) }
let(:user) { create(:user) }
before do
project.team << [user, :master]
login_with(user)
visit namespace_project_tree_path(project.namespace, project, project.default_branch)
end end
step 'I click Blame button' do scenario "can see blame of '.gitignore'" do
click_link ".gitignore"
click_link 'Blame' click_link 'Blame'
end
step 'I should see git file blame' do
expect(page).to have_content "*.rb" expect(page).to have_content "*.rb"
expect(page).to have_content "Dmitriy Zaporozhets" expect(page).to have_content "Dmitriy Zaporozhets"
expect(page).to have_content "Initial commit" expect(page).to have_content "Initial commit"
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment