- Issue created by @longwave
- Status changed to Needs review
8 months ago 9:32pm 23 April 2024 - 🇬🇧United Kingdom longwave UK
Here, we set up a mock service in the data provider, but only to satisfy
assert()
- so if we switch assertions off we can avoid the mock altogether. - Status changed to RTBC
8 months ago 11:48pm 23 April 2024 - 🇬🇧United Kingdom alexpott 🇪🇺🌍
If the test is running in a separate process are the data providers? I guess they must be... just thinking about this to ensure we don't have unintended side effects.
- Status changed to Needs work
8 months ago 6:33am 24 April 2024 - 🇬🇧United Kingdom longwave UK
We could minimise side effects by switching it back on again after creating the data set.
- Status changed to Needs review
8 months ago 8:14am 24 April 2024 - 🇬🇧United Kingdom longwave UK
Implemented #7. Note that we also change
zend.assertions
in FieldTypePluginManagerTest, which is partially where I got the idea for this. - Status changed to RTBC
8 months ago 3:08pm 24 April 2024 - 🇺🇸United States smustgrave
Javascript error appears to be unrelated to this change;.
- Status changed to Fixed
8 months ago 8:03pm 24 April 2024 - 🇬🇧United Kingdom catch
Tricky one but looks sensible.
Committed/pushed to 11.x, thanks!
Automatically closed - issue fixed for 2 weeks with no activity.