DEV: Remove unnecessary `to_not raise_error` from specs

Follow-up to 01cdbd3a13
This commit is contained in:
Gerhard Schlager 2018-12-17 16:10:10 +01:00
parent 5bda4d26b4
commit 2bdbca3801
1 changed files with 5 additions and 5 deletions

View File

@ -14,17 +14,17 @@ describe SiteSettings::Validations do
it "shouldn't raise an error when both buckets are blank" do
change_bucket_value("")
expect { validate("") }.to_not raise_error
validate("")
end
it "shouldn't raise an error when only one bucket is set" do
change_bucket_value("")
expect { validate("my-awesome-bucket") }.to_not raise_error
validate("my-awesome-bucket")
end
it "shouldn't raise an error when both buckets are equal, but use a different path" do
change_bucket_value("my-awesome-bucket/foo")
expect { validate("my-awesome-bucket/bar") }.to_not raise_error
validate("my-awesome-bucket/bar")
end
it "should raise an error when both buckets are equal" do
@ -52,10 +52,10 @@ describe SiteSettings::Validations do
it "shouldn't raise an error when the 's3_backup_bucket' is a subdirectory of 's3_upload_bucket'" do
SiteSetting.s3_upload_bucket = "my-awesome-bucket"
expect { validate("my-awesome-bucket/backups") }.to_not raise_error
validate("my-awesome-bucket/backups")
SiteSetting.s3_upload_bucket = "my-awesome-bucket/foo"
expect { validate("my-awesome-bucket/foo/backups") }.to_not raise_error
validate("my-awesome-bucket/foo/backups")
end
end