gitlab-org--gitlab-foss/spec/controllers/projects/find_file_controller_spec.rb
Peter Leitzen 7b87ed1499 Cleanup usages of JSON.parse in specs
Prefer `json_response` where applicable.
2019-07-16 08:03:49 +00:00

71 lines
1.5 KiB
Ruby

# frozen_string_literal: true
require 'spec_helper'
describe Projects::FindFileController do
let(:project) { create(:project, :repository) }
let(:user) { create(:user) }
before do
sign_in(user)
project.add_maintainer(user)
controller.instance_variable_set(:@project, project)
end
describe "GET #show" do
# Make sure any errors accessing the tree in our views bubble up to this spec
render_views
before do
get(:show,
params: {
namespace_id: project.namespace,
project_id: project,
id: id
})
end
context "valid branch" do
let(:id) { 'master' }
it { is_expected.to respond_with(:success) }
end
context "invalid branch" do
let(:id) { 'invalid-branch' }
it { is_expected.to respond_with(:not_found) }
end
end
describe "GET #list" do
def go(format: 'json')
get :list,
params: {
namespace_id: project.namespace,
project_id: project,
id: id
},
format: format
end
context "valid branch" do
let(:id) { 'master' }
it 'returns an array of file path list' do
go
is_expected.to respond_with(:success)
expect(json_response).not_to eq(nil)
expect(json_response.length).to be >= 0
end
end
context "invalid branch" do
let(:id) { 'invalid-branch' }
it 'responds with status 404' do
go
is_expected.to respond_with(:not_found)
end
end
end
end