Sha256: 85e27e5b810584ee0ad11dcce65076f88fd1c596275eee870283f9d4498cba5a
Contents?: true
Size: 1.83 KB
Versions: 18
Compression:
Stored size: 1.83 KB
Contents
require_relative '../../spec_helper'
require_lib 'reek/examiner'
require_lib 'reek/report/report'
require_lib 'reek/report/formatter'
require 'json'
require 'stringio'
RSpec.describe Reek::Report::CodeClimateReport do
let(:options) { {} }
let(:instance) { Reek::Report::CodeClimateReport.new(options) }
let(:examiner) { Reek::Examiner.new(source) }
before do
instance.add_examiner examiner
end
context 'with empty source' do
let(:source) { '' }
it 'prints an empty string' do
expect { instance.show }.to output('').to_stdout
end
end
context 'with smelly source' do
let(:source) { 'def simple(a) a[3] end' }
it 'prints smells as json' do
expected = <<-EOS.delete("\n")
{\"type\":\"issue\",
\"check_name\":\"UncommunicativeParameterName\",
\"description\":\"simple has the parameter name 'a'\",
\"categories\":[\"Complexity\"],
\"location\":{\"path\":\"string\",\"lines\":{\"begin\":1,\"end\":1}},
\"remediation_points\":150000,
\"content\":{\"body\":\"An `Uncommunicative Parameter Name` is a parameter name that
doesn't communicate its intent well enough.\\n\\nPoor names make it hard for the reader
to build a mental picture of what's going on in the code. They can also be
mis-interpreted; and they hurt the flow of reading, because the reader must slow down
to interpret the names.\\n\"}}\u0000
{\"type\":\"issue\",
\"check_name\":\"UtilityFunction\",
\"description\":\"simple doesn't depend on instance state (maybe move it to another class?)\",
\"categories\":[\"Complexity\"],
\"location\":{\"path\":\"string\",\"lines\":{\"begin\":1,\"end\":1}},
\"remediation_points\":250000,
\"content\":{\"body\":\"A _Utility Function_ is any instance method that has no
dependency on the state of the instance.\\n\"}}\u0000
EOS
expect { instance.show }.to output(expected).to_stdout
end
end
end
Version data entries
18 entries across 18 versions & 1 rubygems