Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Create test for bundle selection. Notice that it requires ajax request, so the test should support javascript.
See parent task.
Comments
Comment #2
fagocreated #2676982: Add support for JS-enabled UI tests for the underlying issue
Comment #3
TR CreditAttribution: TR commentedSee the change records Javascript end-to-end testing and JavascriptTestBase is deprecated in favor of WebDriverTestBase as a starting point for writing these tests.
Also see https://www.drupal.org/docs/8/phpunit/phpunit-javascript-test-writing-tu...
N.B. JavaScript tests are expensive, so these tests should ONLY test the JavaScript behavior - they should NOT be testing things that could be tested in Functional tests.
First, though, the parent issue #2658844: Add Ui for Rules event handlers and per-bundle entities needs to be finished because there's currently nothing to test until the UI is complete.
Comment #4
TR CreditAttribution: TR commentedActually, I don't see any need to keep this issue open. Our usual process is that the tests accompany the patch, except under unusual circumstances. Since Drupal core JavaScript testing was in a state of flux when this issue was raised, that was an unusual circumstance which justified separating the patch from the tests. But as I said in #3 that has all been fixed in Drupal core for a long time now, and there is no longer a reason to have a separate issue for the patch and for the test.
So tests for features introduced by #2658844: Add Ui for Rules event handlers and per-bundle entities should be included with #2658844: Add Ui for Rules event handlers and per-bundle entities. Bundling the tests with that patch will also help ensure that any patch we commit behaves as expected.
Marking this as a duplicate of #2658844: Add Ui for Rules event handlers and per-bundle entities