Revision d6c08a7a
Added by Daniel Lobato Garcia over 8 years ago
| test/unit/compute_profile_test.rb | ||
|---|---|---|
|
User.current = users :admin
|
||
|
end
|
||
|
|
||
|
test "name can't be blank" do
|
||
|
cp = ComputeProfile.new :name => " "
|
||
|
assert !cp.save
|
||
|
end
|
||
|
|
||
|
test "name must be unique" do
|
||
|
cp = ComputeProfile.new :name => "1-Small"
|
||
|
assert !cp.save
|
||
|
end
|
||
|
should validate_presence_of(:name)
|
||
|
should validate_uniqueness_of(:name)
|
||
|
should_not allow_value(' ').for(:name)
|
||
|
|
||
|
test "should not destroy if in use by hostgroup" do
|
||
|
#hostgroups(:common) uses compute_profiles(:one)
|
||
Also available in: Unified diff
Fixes #11618 - Replace validation tests by shoulda-matchers
A good chunk of our unit tests are testing whether a validation is
working or not by testing it actively. For the validations we've
added ourselves I would say it's fine. However for validations that
come from the Rails framework, we're essentially testing their job.
Instead of testing (for instance) validates(:name, :uniqueness =>
true) by creating two objects and verifying the second one won't
save (these tests are already done at the framework level), we
should simply test we're including validations in our models.
The well-maintained gem shoulda-matchers provide easy functions to
check we're including such validations, and other helpers we can
use to refactor our tests further and not test Rails functionality
twice.