Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.For LibrariesUnitTest the extended class Drupal\simpletest\DrupalUnitTestBase no longer exists as per this change notice https://www.drupal.org/node/2271271 and the Dec 5th commit in #2388043: Remove DrupalUnitTestBase. This not only causes the Libraries API test to fail but it also causes a fatal error when loading the test list in the UI or when running any tests for modules that depend on Libraries API (e.g. with d.o. testbots, etc.). Marking an major since this has ramifications on the ability to load any tests, not just tests from this module.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | libraries-drupalunittestbase_removed-2390301-1.patch | 535 bytes | rjacobs |
Comments
Comment #1
rjacobs CreditAttribution: rjacobs commentedHere's a patch with a simple name change for the class used.
I don't think tests will pass however, as it looks like there are other test issues with some functional tests (unrelated to this issue). Meh, let's see what the testbots do.
Comment #2
rjacobs CreditAttribution: rjacobs commentedYep, test status "postponed". Anyway, I hope someone will still be able to have a look at this as I don't think the other test issues should hold this up if at all possible.
Comment #3
yukare CreditAttribution: yukare commentedWe need this commited before working on other errors in tests. This make impossible to run the tests for ANY module that depends on libraries.
This patch fixes the fatal error, the others error are related to other issues, like the removal of url().
Comment #4
rjacobs CreditAttribution: rjacobs commentedUpdated the summary based on the previous comment. Though I can apply this patch to get tests working on my dev space I see now that it's currently impossible to run any of my tests on d.o.
Comment #5
tstoecklerAwesome, thanks a lot.
Committed to 8.x-3.x
Comment #8
rjacobs CreditAttribution: rjacobs commentedThanks!
I think the system applied status change (to "needs work") was because the testbots were trying to test the patch against a repo snapshot that already contained the patch. I believe its safe to re-apply the "fixed" status.
To confirm, my own tests that depend on Libraries API are no longer failing because of this issue. Thanks again.