If there is an error when executing the method under test, then this
test caused the downstream test \remoteapicore_test::test_getBacklinks
to unexpectedly fail. Probably, because the global plugin controller
would not have been reset to its original value.
Running this test in its own process ensures that it won't affect any
other test, even if it messes with the global state and doesn't clean up.
On PHP8 trying to access a non-existing array key leads to a warning,
which we might treat as errors?
This incidentally also fixes another test downstream which broke because
this rendering test changes the global plugin controller, but doesn't
clean it up that if the test errors.
-9000 is used as the position to make it obvious that this number is
meaningless for this test.
This commit fixes all E_STRICT messages shown when running the test
suite. There might be more problems not covered by tests, yet.
For compatibility reasons with plugins, E_STRICT errors are still
supressed.
Michael Große