Our Drupal brethren have gone through a series of tasks over the years of the D8/D9 cycle, each one introducing a new way to test JS, and deprecating the previous way:
- Javascript end-to-end testing added (JavascriptTestBase), using Phantomjs (introduced in D8.1 / change record / https://www.drupal.org/project/drupal/issues/2469713 / https://www.drupal.org/project/drupal/issues/2702661)
- Test Drupal using webDriver/selenium/chromedriver (introduced in D8.5 / change record / https://www.drupal.org/project/drupal/issues/2775653)
- JavascriptTestBase deprecated in favor of WebDriverTestBase (change record / https://www.drupal.org/project/drupal/issues/2942900 / https://www.drupal.org/project/drupal/issues/3088688)
It is my understanding that there is no JS testing in D7/Backdrop, and that we rely on manual testing when it comes to it. This issue here is to discuss and decide whether we should introduce a framework to be testing JS in Backdrop.
Pros
- no more tedious/manual tests for JS functionality
- leverage any tests already in D8+ that also apply to us (like tests for
#statesfor example: #5161) - ...?
Cons
- introducing dependencies to run tests
- increase in time for automated tests to run
- ...?
GitHub Issue #:
5160
Recent comments
RE: duplicate files —If an image is disassociated from any content, the system will delete it after x number of hours. (Six, I believe.)
Problem with Field image • Select existing file
For now, I’ve switched to the Seven theme. It’s a very good theme, too. Finally, "select existing file" is important. Otherwise, you end up loading tons of unnecessary, duplicate...
Problem with Field image • Select existing file
Oh, thank you! I have also been frustrated with this, but haven't tried since switching from Gin theme.
Problem with Field image • Select existing file