Add Fast404PathTestCase for testing paths fast404_path_check
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | fast404-2715585-13.patch | 2.04 KB | gg4 |
| #2 | 2715585-2.patch | 2.35 KB | naveenvalecha |
Add Fast404PathTestCase for testing paths fast404_path_check
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | fast404-2715585-13.patch | 2.04 KB | gg4 |
| #2 | 2715585-2.patch | 2.35 KB | naveenvalecha |
Comments
Comment #2
naveenvalechaAttached patch would work but the fast404 is not sending the fast404 output in the case of the paths.this might be proably due to the Event Subscriber weight but not sure about that.
Comment #3
naveenvalechaThe patch N/W as per #2
Comment #4
gg4 commentedWhy is this commented out?
Comment #5
damienmckennaI suspect the problem may be that adding some values in Settings may not make it available to the entire system. Certainly this line seems irrelevant:
I would suggest start with looking into core's KeyValue system, see how to store settings there.
(BICBW)
Comment #6
gg4 commentedI think there is probably a better way to handle settings in these tests in general. I am really meaning to get to adding test coverage for this module so we can get to a stable release.
Comment #7
gg4 commentedbut, yea, this should probably just be:
Comment #8
robpowellCouldn't get phpunit running reliably locally, going to get the test bot to hit this.
Comment #9
robpowellComment #11
gg4 commentedComment #13
gg4 commentedComment #15
gg4 commentedPageCacheTesthas some good examples of how to handle settings in functional tests.