Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
comment.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Sep 2008 at 00:11 UTC
Updated:
7 Dec 2008 at 16:12 UTC
Jump to comment: Most recent file
Comments
Comment #1
cwgordon7 commentedTest case attached to demonstrate point.
Comment #2
lilou commentedPatch no longer applies.
Comment #3
cwgordon7 commentedExcept that it does.
Comment #4
cwgordon7 commented(It's just fuzz, but reroll attached. :P)
Comment #5
maartenvg commentedI wrapped the message in a user_access('administer comments') check, which solves this little issue and should not change the comment approval process. BTW, I left the test.
Comment #6
Anonymous (not verified) commentedThe last submitted patch failed testing.
Comment #7
maartenvg commentedThe automated testing failed because of #334826: Editing of anonymous comments is broken, so review that patch to get it in and set this back to CNR.
Comment #8
maartenvg commentedThat bug was just committed, so it's reviewing time again!
Comment #9
catchPatch passes tests, and it's lovely. That message is really annoying if you've just unpublished a comment.
Comment #10
dries commentedThis is one of those cases where I'm not 100% convinced we need to have a test.
Comment #11
webchicktsk, tsk. ;)
I think having the test is good, both because it helps http://acquia.com/files/test-results/modules_comment_comment.module.html get to 100%, but also because it's one of those things that's not tested in the day-to-day operation of Drupal very often, so is a good candidate for something that might subtly break 60 patches down the line.
How about we re-roll for the missing space and see if we come to consensus about the tests in the meantime? ;)
Comment #12
catchThe shame! Re-rolled for the space. I don't think it hurts to have trivial-ish tests in there - when we get close to 100% coverage, we'll hopefully be trying to fill in the gaps, and knowing that an area is 'don't bother testing' will be near impossible - so better to have a test than not have one and have the same thing duplicated again in 3 months.
Comment #13
cwgordon7 commentedI actually have to agree with Dries in this case. I don't think the test case is at all applicable for any bug other than this one: it's a good way to determine whether or not the patch actually fixes the bug in question, but it doesn't have any real use in core. All it does is make sure that after an administrator updates an unpublished comment, this specific message does not appear. I highly doubt that that will ever fail again unless this patch is reverted after applied. I don't think the hunk of this patch in comment.test should be committed, at least not in the current state. If we want to have a test case for this, it needs to be much more generalized—checking for a specific bug doesn't help our test coverage in the long run.
Comment #14
maartenvg commentedoh my, a (more or less) 1 line patch and I manage to get even that not perfect :P
I agree with Dries and Charlie, the test case is too specific for this bug, which probably will never surface again. It has nothing to do with general functionality of Drupal as a whole.
Comment #15
webchickOk, I committed #12 without the test case. If even the author of the test case agrees it is unnecessary, then.. ;P
Thanks folks! :)