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.
Problem/Motivation
@dawehner spotted this whilst we were waiting for a test run to finish.
19:20:10 Drupal\Tests\settings_tray\FunctionalJavascript\QuickEditInt 2 passes
19:25:22 Drupal\Tests\settings_tray\FunctionalJavascript\SettingsTray 22 passes
That's way longer than any other JS test.
Proposed resolution
Don;t use a data provider. They are really for a unit tests. Using them in functional tests means we have to do a full re-install each time.
Remaining tasks
User interface changes
none
API changes
none
Data model changes
none
Comment | File | Size | Author |
---|---|---|---|
#18 | 2971472-10.patch | 2.49 KB | Anonymous (not verified) |
#17 | 2971472-14_SLOW_DRUPAL.patch | 3.36 KB | Anonymous (not verified) |
| |||
#17 | no_changes_SLOW_DRUPAL.patch | 889 bytes | Anonymous (not verified) |
| |||
#14 | interdiff-2971472-10-14.txt | 877 bytes | tedbow |
#14 | 2971472-14_SLOW_DRUPAL.patch | 3.35 KB | tedbow |
Comments
Comment #2
alexpottWrong test name - doh.
Comment #3
alexpottLet's see how much time this saves. Note that JS tests are not run concurrently.
Comment #4
alexpottComment #5
alexpottSo it's still long but it is 2 mins quicker.
Comment #6
dawehnerThank you alex!
Comment #7
Anonymous (not verified) CreditAttribution: Anonymous commentedReally, very elegant! Better than my attempt at #2942900-61: Convert JavascriptTestBase Tests to use DrupalSelenium2Driver. But it would be nice to add to
doTestBlocks()
:To eliminate the random fail described in the #2902191-11: Determine cause and fix random fail in \Drupal\Tests\settings_tray\FunctionalJavascript\SettingsTrayBlockFormTest::testBlocks.
Comment #8
borisson_This can be protected now, instead of a public method.
I don't really understand what @vaplas is saying in #7, but hopefully @alexpott or @dawehner do understand that :)
Comment #9
alexpottThanks for the reviews @vaplas and @borisson_
Comment #10
alexpottWhoops ignore the patches from #9 - it's the same as #3. Correct patch and interdiff.
Comment #11
googletorp CreditAttribution: googletorp as a volunteer and at Reveal IT commentedI think this is good to go.
Comment #12
Anonymous (not verified) CreditAttribution: Anonymous commented#8: 😀
RTBC++
Comment #14
tedbowI think the last test failure was
I just checking on this issue to make sure it wasn't going to cause a random failure like in #2902191: Determine cause and fix random fail in \Drupal\Tests\settings_tray\FunctionalJavascript\SettingsTrayBlockFormTest::testBlocks.
This is great solution!
This patch looks good.
Going to upload "slow drupal" patch we were able to help debug some of the random failures by running the test multiple times with
usleep()
call in index.php.Just figure we should try just in case in the past we only found the random failures when DrupalCi was running slow.
So attached 2 "SLOW_DRUPAL" patches once with the test changes and once without. If they both pass then I think we can RTBC with #10 again.
Comment #17
Anonymous (not verified) CreditAttribution: Anonymous commentedIn the #13 fail, all tests were successful, but information about them was lost. This problem has recently appeared more often.
outside_in 😉 Reroll.
Comment #18
Anonymous (not verified) CreditAttribution: Anonymous commentedAll good. Reupload #10.
Comment #19
catchCommitted 1ef022e and pushed to 8.6.x. Thanks!