Automated testing fails and returns a deprecation notice after running "Drupal\Tests\multiselect\FunctionalJavascript\MultiselectElementJavascriptTest ". Deprecation notice returns "Drupal\FunctionalJavascriptTests\JavascriptTestBase is deprecated in Drupal 8.5.x and will be removed before Drupal 9.0.0. Instead, use Drupal\FunctionalJavascriptTests\WebDriverTestBase." See attached screenshot.
It seems like we should change "JavascriptTestBase" to "WebDriverTestBase" as it suggests in the notice.
Steps to test:
1) Navigate to 'admin/config/development/testing'
2) Select "Multiselect" check box
3) Scroll down to bottom of list and click "Run tests"
Patch to follow.
Comment | File | Size | Author |
---|---|---|---|
#2 | testing-error-2992045-2.patch | 781 bytes | dani3lr0se |
| |||
multiselect-testing-error.png | 265.76 KB | dani3lr0se |
Comments
Comment #2
dani3lr0se CreditAttribution: dani3lr0se at Hook 42 commentedHere is a patch for review. Changing "JavascriptTestBase" to "WebDriverTestBase" makes the test pass. Seems like the problem is solved after changing the name.
Comment #3
dani3lr0se CreditAttribution: dani3lr0se at Hook 42 commentedComment #4
volkswagenchickThe patch applied using simplytest.me.
When I " Navigate to 'admin/config/development/testing' " - I am taken to a page not found...are there more steps to reproduce?
Comment #5
dani3lr0se CreditAttribution: dani3lr0se at Hook 42 commented@volkswagenchick, I know we've chatted already, I just wanted to make a note here. We just need to enable the testing module in core. Thanks for reviewing. :)
Comment #7
nerdsteinThis may seem odd but the testbot doesnt seem to be using the new patch, which should fix the testing error.
I'm going to merge this in and, hopefully, it addresses the issue. We'll patch forward with any issues.
Comment #9
nerdsteinPatch merged, we'll move forward with anything else needed. Closing for now.
Comment #11
Kristen PolPer a Slack discussion with Gábor Hojtsy regarding usage of D9 tags (Drupal 9, Drupal 9 compatibility, Drupal 9 readiness, etc.), "Drupal 9 compatibility" should be used for contributed projects that need updating and "Drupal 9" was the old tag for D8 issues before the D9 branch was ready. Doing tag cleanup here based on that discussion.