comment.test includes a one line reference to comment controls, that'll need to be taken out if #175841 gets committed.
I need to get up to speed on SimpleTest so might as well start by trying not to break existing tests. No patch yet but this will remind me to do it.
Not sure what the deal is with statuses, so marking postponed because this won't get committed until the core issue does.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | comment.test.patch | 8.24 KB | aaronbauman |
| #3 | controls-test.patch | 1009 bytes | catch |
Comments
Comment #1
boombatower commentedThanks for making this issue.
Comment #2
catchOK so that patch has got in, but it looks like setCommentForm is mixing up two different settings anyway.
The position of the comment form (on the same page as the node/comments or on a separate page) is a completely different issue to whether comment controls were enabled or disabled and their position (above, below or both).
Should probably be something like this (completely untested).
Have to say this vindicates how confusing comment controls were though....
Comment #3
catchI appreciate the irony of uploading an untested patch to the SimpleTest issue queue and hang my head in shame. Won't have time to try tests etc. until at least this weekend. Hopefully this is trivial enough that I didn't do anything stupid.
Comment #4
boombatower commentedI'm curious why this doesn't cause an error when the patch is not applied. Any thoughts?
Comment #5
catchHad a quick look although still only time for visual review, comment module uses the
COMMENT_FORM_SEPARATE_PAGEconstant in nearly all cases except for the very end of comment_render.Additionally, testFormOnPage only verifies that
setCommentForm(TRUE)results in the comment form being rendered on the page (which it should because that bit's right), it doesn't check the converse. This explains why the tests were passing I guess.Also, moving to core!
Comment #6
catchcomment settings are per node type, so this is more wrong than I originally thought. Moving to tests component.
Comment #7
catchRetitling this since although the comment controls are mentioned, that's just a symptom of a wider problem in the test - this section bears no resemblance to what actually happens in core at all.
Also marking postponed pending this general cleanup: http://drupal.org/node/251843
Comment #8
catchThe comment form location is now a per-node-type setting. This isn't reflected in the current comment.test - so it needs changing to use the proper variables, and then a check to ensure the form shows up on the correct pages.
Comment #9
aaronbaumanComment #10
aaronbaumanPlease see the patch submitted to #296483: TestingParty08: paged comments. This patch addresses the per-node visibility of the Comment form.
Comment #12
aaronbaumanOK, System Message, if you insist I will re-post
Comment #13
aaronbaumanComment #14
boombatower commentedIs that the same test from the other issue? If so then just finish in that issue and then we can mark this one as fixed...so for now lets mark this a postponed.
Comment #15
catchComment #16
aaronbaumanComment #17
boombatower commentedShould be re-evaluated against 8.x to see if still necessary and if so committed and backported.
Comment #18
aspilicious commentedChecked these tests, they are alrdy incorporated in drupal core in some way. :)