Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
image.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
24 Nov 2009 at 19:23 UTC
Updated:
3 Jan 2014 at 00:29 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
johnalbinIn IRC, catch pointed out that using call_user_func is nearly always bad. This is his suggested solution.
Comment #2
yoroy commentedEncountered the same error, applied the pach, error gone. RTBC since I trust catch and john to write the right code :)
Comment #3
dries commentedCommitted to CVS HEAD, but this should have been testing. Setting to 'needs work' for tests.
Comment #4
matt2000 commentedHere's a test.
Comment #7
aspilicious commentedString translate, search and validate (LocaleTranslationFunctionalTest) [Locale] 314 2 0
Message Group Filename Line Function Status
JavaScript file created: not found Other locale.test 347 LocaleTranslationFunctionalTest->testJavaScriptTranslation()
JavaScript file rebuilt: not found Other locale.test 354 LocaleTranslationFunctionalTest->testJavaScriptTranslation()
This has to be fixed o_0....
This isn't related at all with the patch...
I don't know s*** about the test bot, so i can't give suggestions
Comment #8
sun.core commentedTests are not critical. Please read and understand Priority levels of Issues, thanks.
Would be great to get this sucker in though. :)
Comment #9
Freso commentedThis breaks the 80 character wall. The first line should be a short (<77 characters) summary, which could be followed be a more in-depth explanation.
Nit-pick: We want these descriptions to end with a period. :)
That's really all I can point at. I think I get the test, and I don't think there's anything wrong with it - but it still needs to be tested on an install without the #1 patch (
patch -R), to make sure it the test cries error (if it doesn't, the test doesn't test for the thing the patch patched). I'd be happy to RTBC with proper Doxygen and the bot's "yay" though, but having tested without the patch would be a huge bonus.Powered by Dreditor.
Comment #10
yoroy commentedOnly fixing the 80 char line and the period pointed out in #9
Comment #12
matt2000 commented#10: patch.patch queued for re-testing.
Comment #14
matt2000 commentedFixed the PHP error (by renaming the class), optimized, and updated to test the same way file.test does.
Comment #15
matt2000 commentedComment #16
Freso commentedThis really just needs a review to see if the test fails without the patch (from #1), as the testing bot takes care to test it against HEAD. No one wants to do this?
Should also have an trailing period. :)
Stray whitespaces.
148 critical left. Go review some!
Comment #17
matt2000 commentedHere's the fixes.
I tried to get a checkout as of 2009-11-24 for running the test w/o the patch, but could not get it to bootstrap....
Comment #18
Freso commentedI was thinking more of something like:
That way, the rest of the code should also be up-to-date. Of course, if anything has been applied "on top of" that patch, hunks might fail in reversing (-R) the patch.
Comment #20
eojthebraveI believe the tests added here cover this as well. If not let me know and I can help get this sorted out. #601966: Tests for image field, specifically
testImageFieldFormatters()which uploads an image to the article content type and tests the various image field formatters.Comment #21
johnmurray commented#1: image-effect-apply-641750-1.patch queued for re-testing.
Comment #22
fool2 commented#1: image-effect-apply-641750-1.patch queued for re-testing.
Comment #23
the_paulus commentedI have reviewed the code and the test has passed.
Comment #24
stupiddingo commentedhttp://drupal.org/files/issues/image-effect-apply-641750-1.patch tested and passed review by the_paulus in #23 setting status to reviewed & tested by the community.
Comment #25
chrowe commented#1: image-effect-apply-641750-1.patch queued for re-testing.
Comment #26
stupiddingo commentedFeel that I should add that I too reviewed this and it passed all image tests.
Comment #27
eojthebraveI'm a little bit lost and not sure what is being tested/reviewed here.
If we are still talking about the tests in #17, or #4 I don't think these are necessary anymore. We added a set of almost identical tests in #601966: Tests for image field, which not only check that the image is displayed using the default formatter but all the other formatters as well.
See
function testImageFieldFormatters()in modules/image/image.testI think it is safe to say that the testing portion of this issue is covered, and if that's the only reason this issue is still open we should close it.
Comment #28
dries commented#17: article_image_test_02.patch queued for re-testing.
Comment #29
kcybulski commented#17: article_image_test_02.patch queued for re-testing.
Comment #30
dries commentedBased on #27, it feels like this needs more discussion.
Comment #31
alexweber commentedBased on #1, #2 and #3 and given that the test is no longer necessary because of #27 I think we can safely commit & close this.
Comment #32
eojthebraveYeah. I agree that this issue can probably be closed. The code to fix the original issue was already committed, see comment #3, and test coverage for this was added in another issue. #601966: Tests for image field
Comment #33
xjmClosing as fixed.