Sha256: 7eeb929baa6d0979e85645358ab8428c4ffd6403f5b50d16d32d3c4109975638
Contents?: true
Size: 1.42 KB
Versions: 32
Compression:
Stored size: 1.42 KB
Contents
require 'spec_helper'
describe Krikri::AggregationEntityBehavior do
before do
# The harvest activity is the activity that generated the entities upon
# which the mapping activity below has acted. I suppose we could mock the
# call that will happen to EntityConsumer#assign_generator_activity! when
# Krikri::Mapper::Agent is instantiated, but that seems like jumping
# through more hoops and making this less comprehensible than it is now.
DatabaseCleaner.clean_with(:truncation)
create(:krikri_harvest_activity)
end
describe '#entities' do
let(:mapped_record_uri) { double('record uri') }
let(:agg_record_double) { instance_double(DPLA::MAP::Aggregation) }
let(:activity) { create(:krikri_mapping_activity) }
it 'enumerates generated entities' do
allow(activity).to receive(:entity_uris)
.and_return([mapped_record_uri])
allow(DPLA::MAP::Aggregation).to receive(:new)
.with(mapped_record_uri)
.and_return(agg_record_double)
# Circumvent Marmotta request with #get call in
# AggregationEntityBehavior#entities
allow(agg_record_double).to receive(:get).and_return(true)
agg = activity.entities.first
# Just so it's clear, this just proves that the code in
# AggregationEntityBehavior#entities was executed, not that
# what's coming back from Marmotta is correct.
expect(agg).to eq(agg_record_double)
end
end
end
Version data entries
32 entries across 32 versions & 1 rubygems