1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
# frozen_string_literal: true
require "spec_helper"
require_migration!
RSpec.describe ScheduleMigrateSharedVulnerabilityScanners, :migration do
describe "#up" do
before do
migrate!
end
it "schedules" do
expect(described_class::MIGRATION).to have_scheduled_batched_migration(
table_name: described_class::TABLE_NAME,
column_name: described_class::BATCH_COLUMN,
interval: described_class::DELAY_INTERVAL,
batch_size: described_class::BATCH_SIZE,
max_batch_size: described_class::BATCH_SIZE,
sub_batch_size: described_class::SUB_BATCH_SIZE,
gitlab_schema: :gitlab_main
)
end
describe "ID range" do
let(:expected_range) do
{ min_value: described_class::BATCH_MIN_VALUE,
max_value: described_class::BATCH_MAX_VALUE }
end
subject do
Gitlab::Database::BackgroundMigration::BatchedMigration
.for_configuration(:gitlab_main,
described_class::MIGRATION,
described_class::TABLE_NAME,
described_class::BATCH_COLUMN,
[])
end
it "is set" do
# The `have_scheduled_batched_migration` matcher accepts the
# `batch_min_value` and `batch_max_value` keywords. However the respective
# column names are `min_value` and `max_value`. Hence the matcher cannot
# be used in this case, as it asserts the wrong attributes.
expect(subject).to all(have_attributes(expected_range))
end
end
end
describe '#down' do
before do
schema_migrate_down!
end
it "deletes" do
expect(described_class::MIGRATION).not_to have_scheduled_batched_migration
end
end
end
|
