-
Notifications
You must be signed in to change notification settings - Fork 898
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Notifications None #18035
Fix Notifications None #18035
Conversation
|
||
describe "#enabled?" do | ||
it "detects properly" do | ||
expect(FactoryGirl.create(:notification_type, :audience => NotificationType::AUDIENCE_USER)).to be_enabled |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does these tests need to create
?
How is enabled?
related? Should it instead test instance.valid?
?
If not, should the enabled?
tests test against all of the audiences?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I was testing the side effect of save.
not very straight forward
fixes ebd613a The notification type "NONE" was introduced, but it was not part of basic validations https://bugzilla.redhat.com/show_bug.cgi?id=1535177
c1ba423
to
acd0a19
Compare
Checked commit kbrock@acd0a19 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
Fix Notifications None (cherry picked from commit 8489078) https://bugzilla.redhat.com/show_bug.cgi?id=1535177
Hammer backport details:
|
The notification type
"NONE"
(AUDIENCE_NONE
) was introduced in #17673 , but it was not part of basic validationsThis was causing the RFE to fail:
https://bugzilla.redhat.com/show_bug.cgi?id=1535177