Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
base system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
14 Aug 2015 at 09:38 UTC
Updated:
1 Sep 2015 at 09:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
alexpottComment #3
alexpottHere's a patch...
This works when you do:
Comment #4
alexpottNo for the patch.
Comment #5
alexpottFound some more in several module's unit tests.
Comment #6
dawehnerIdeally we would kinda assert that we don't have new entries coming in. If we move this onto a method dedicated tests could opt out of that checking.
Comment #7
alexpott@dawehner yes good idea. I think it is too early for that since there is still some left. The other SafeMarkup method removal issues should completely tidy that up. I'll open a followup.
Comment #8
dawehnerFair point. Let's do that later.
Comment #9
dawehnerAlex is working on some additional test coverage.
Comment #10
alexpottTest-only patch is the interdiff. Created a general listener folder instead of specific standards one cause it seems pointless.
By adding the SafeMarkupSideEffects listener we can ensure that no test pollutes the SafeMarkup list in the data providers.
Comment #11
alexpottIt'll be interesting to see what our test runner does with an exception thrown uncaught from phpunit.
Comment #13
alexpottSweet! the test breaks HEAD and the patch is green.
Comment #14
wim leersPHPUnit++
Nit: s/effects/affects/
+1
I don't think this even needs to be a safe string.
These suggest that too.
Comment #15
wim leersI especially like how the added listener will prevent similarly fragile tests from being added! :)
Comment #16
alexpottThanks @Wim Leers.
1. :)
2. Fixed
3. :)
4. & 5: Added a comment.
Comment #17
alexpottVery small doc improvement.
Comment #19
wim leersComment #21
wim leersAutomatically rebased, thank you git.
Comment #24
stefan.r commentedStill green so back to RTBC.
Comment #25
catchCommitted/pushed to 8.0.x, thanks!