Sha256: 35f9f45298ff02a4c3c0c793aaf5d1b7aefde0e3de144f36ab20d0606e07c149
Contents?: true
Size: 1.35 KB
Versions: 17
Compression:
Stored size: 1.35 KB
Contents
# encoding: utf-8
require 'spec_helper'
# this tests check how well rails_admin_settings handles settings disappearing from DB during execution
# real usage: app specs with database_cleaner enabled
describe 'Database trickery' do
it "should handle settings disappearing from DB" do
email = "my@mail.ru"
email2 = "my2@mail.ru"
Settings.email = email
Settings.email.should == email
RailsAdminSettings::Setting.destroy_all
# settings are still cached
Settings.email.should == email
Settings.email = email2
Settings.email.should == email2
end
it "should handle settings appearing in DB when settings are loaded" do
Settings.tst2.should == ''
RailsAdminSettings::Setting.create!(key: 'tst', raw: 'tst')
# settings are still cached, but when we try to create a setting it sees updated value in DB
Settings.tst.should == 'tst'
end
it "should handle settings appearing in DB when settings are not loaded" do
RailsAdminSettings::Setting.create(key: 'tst', raw: 'tst')
Settings.tst = 'str'
Settings.tst.should == 'str'
end
it "#destroy_all!" do
Settings.tst = 'str'
Settings.destroy_all!
Settings.tst.should == ''
end
it "#destroy!" do
Settings.tst = 'str'
Settings.tst2 = 'str2'
Settings.destroy!(:tst)
Settings.tst.should == ''
Settings.tst2.should == 'str2'
end
end
Version data entries
17 entries across 17 versions & 1 rubygems