Closed (duplicate)
Project:
Drupal core
Version:
8.9.x-dev
Component:
node system
Priority:
Minor
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
7 Sep 2019 at 16:00 UTC
Updated:
28 Mar 2020 at 06:15 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
jungleSubmit the patch
Comment #4
dwwRe-queued for a more recent test run. I'd expect the # of passed assertions to go up relative to the branch values. But these test results are so stale, I can't tell. ;)
Comment #5
dwwHrm, weird:
https://www.drupal.org/pift-ci-job/1623474
"28,260 pass" for both the patch and the latest from the branch. So it seems like this test class is already being automatically discovered and run. At least by run-tests.sh and the d.o testbot. Seems worth doing to match conventions, but I don't think the summary is entirely accurate.
Comment #6
jungleThanks for reviewing @dww! Nice catch!
Comment #7
dww@jungle Re: #6: Cool, thanks for the updates.
I don't see a reason not to do this. Tentatively setting RTBC. Let's see what the core committers say. :)
Comment #8
jungleCheers! BTW, a similar one I filed, but it seems #3079860 could be closed as I just checked they made a BC layer against 8.9.x
Comment #9
alexpottTest discovery doesn't rely on the class ending in Test - if you search the current qa logs for "TestSettingSummaries" you'll find this test is running. However there is an issue to make this true... see #2296635: Evaluate performance impact of limiting test discovery to *Test.php filename suffix - in fact this issue is a straight up duplicate of that issue and there are other classes to fix.