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
You can edit images and load them back to the same folder with the same name and extension, this will not create a problem. Replace directly in the file system, without the use of CMS, for CMS...
Image manipulation on server?
I was under the impression you could not do that - don't know where I got that idea from... thought it had to do with the way Backdrop manages image files.
Image manipulation on server?
I think given the warning on the source site: At this time, if your new project can afford to require PHP 5.5+, which it should, please use PHP's native password_hash() /...
July 31, 2025