The comment tests should be enhanced to ensure that
- Users can post a comment and solve a CAPTCHA in one shot.
- Moderators can update an existing comment without errors.
| Comment | File | Size | Author |
|---|---|---|---|
| #21 | mollom.data-update.21.patch | 4.98 KB | sun |
| #17 | mollom.data-update.17.patch | 4.93 KB | sun |
| #17 | mollom.data-update.17.tests-only.patch | 4.46 KB | sun |
| #15 | mollom.data-update.15.patch | 5.92 KB | sun |
| #14 | mollom.data-update.14.patch | 5.74 KB | sun |
Comments
Comment #2
sunSorry, wrong patch format. Still need to fix all of my scripted automations.
Comment #4
sunAlright. Windows 7 keeps on to drive me nuts.
Comment #5
sunComment #6
dries commentedThis looks good to me. It wasn't clear how you identified these missing tests though. Any particular motivation?
Comment #7
sunCause for this was a bug report filed in http://mollom.zendesk.com/tickets/2159
Comment #8
dries commentedCommitted to master (7.x-1.x) and 7.x-rest. Thanks sun!
I guess we could consider back-porting this patch to D6.
Comment #9
sunBack to the drawing board. Further analysis on the support issue revealed:
Need to figure out how to properly catch this situation in a test...
Comment #10
AimAdvantage commentedsubscribe
Comment #11
sunWork on the tests revealed a quite major problem/bug with the node form integration - we're not storing any Mollom data for nodes, and Node API/Form API doesn't allow us to fix it.
Comment #12
sunAttached patch cleanly reproduces the bug.
Comment #13
sunLet's make the testbot confirm that the tests in this patch fail.
Comment #14
sunAnd attached patch additionally fixes the bug.
Comment #15
sunSlight comment tweaks.
Comment #16
sunI've extracted that essential node form integration fix into #674692: Node module integration tests
Comment #17
sunSince we've learned that this is a bug in Mollom module's low-level CRUD handling of session data, I've revamped the tests to remove the dependency on Node and Comment modules, and instead, directly test the API functions.
Much cleaner now.
Comment #19
sunComment #20
dries commentedThis looks good. My only comment is that we never actually change $data1 so it might not be properly updating the existing record. The test can probably be improved in that regard.
I think the patch can be committed as is though -- it's an improvement over what we currently have so we shouldn't hold this up. Good work.
Comment #21
sunIndeed, that was a bit sloppy. Fixed in attached patch.
Thanks for reporting, reviewing, and testing! Committed to all branches.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.