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.
@D7csmtl
Related issue: http://drupal.org/node/601308
Because garland is the default theme, and it over-rides lots of templates, tests in node.test were not breaking on broken html code in the node.tpl.php found in node.module. To get around this, I propose we use the Stark theme as the default theme in simpletest. Thanks to Omar who put me on to this idea.
Marked as critical, because I feel it is, but feel free to downgrade.
Comment | File | Size | Author |
---|---|---|---|
#23 | use-stark-for-testing-719814-22.patch | 1.07 KB | sfyn |
#17 | add-tests-to-default-templates-719814-17.patch | 597 bytes | rjgoldsborough |
#15 | 719814-drupal-badcamp-testing-profile-use-stark-theme-15.patch | 597 bytes | mlncn |
#5 | simpletest-719814-5.patch | 583 bytes | sfyn |
#1 | simpletest-719814-1.patch | 545 bytes | sfyn |
Comments
Comment #1
sfyn CreditAttribution: sfyn commented@D7csmtl
Here is my patch to use stark as the simpletest default theme.
Comment #2
sfyn CreditAttribution: sfyn commentedComment #3
sfyn CreditAttribution: sfyn commentedGo testbot go
Comment #5
sfyn CreditAttribution: sfyn commentedreroll
Comment #7
sfyn CreditAttribution: sfyn commentedLooking at the details of this patch I am impressed at how many fails it generated. I'm calling it a night because I'm not sure where to start right now.
UPDATE
I had a look at some of the failing tests:
Overall, 14 test cases had fails. Most of these on a few lines of code, repeatedly. I will have a try at getting more passes out of this patch over the next few days.
Comment #8
sfyn CreditAttribution: sfyn commentedTagged as part of the Drupal 7 Montreal codesprint
Comment #9
boombatower CreditAttribution: boombatower commentedErr...what!? We are far beyond making such a significant change for D7.
Comment #10
sfyn CreditAttribution: sfyn commentedI understand that this is a significant change, but I am worried about broken templates sneaking into the final release. I would like to try reworking the 14 failing test cases . . .
But if its going on to Drupal 8, how about allowing tests to run under a theme chosen when you launch testing / or by default testing under each core theme?
Comment #11
sfyn CreditAttribution: sfyn commentedWithout knowing the current state of this in 8, I am bumping up to major in the hopes it gets some attention.
Comment #12
Lars Toomre CreditAttribution: Lars Toomre commentedThis bug came up for me today on bug bingo; hence, my response here.
The Drupal SimpleTest methodology seems exhaustively to run all tests before a new patch is applied. I would hope/expect that all theme-related tests are run against all themes that are included as part of a Drupal distribution. Similarly, I would expect that all "plugable" code elements are tested before a patch is said to 'pass'. Hence, I would think that this patch is just a subset of selecting one theme array element from a list of several core themes.
While it has been some time since the proposed patch was last rolled, I am bothered that such a simple change would break so many tests. I would suggest that the next roll of this patch check each and every one of the themes included Drupal 7/8.
Comment #13
tstoecklerNow that we have the testing profile, we should use that.
Basically just add the code from the patch above to testing_install().
Comment #14
sunThis is a task, not a bug.
Comment #15
mlncn CreditAttribution: mlncn commentedArrived at tstoeckler's conclusions independently (here at BADCamp with Scor, Webchick, Jacine), and here is the patch.
Comment #16
xjmTagging as novice for the task of rerolling the Drupal 8.x patch on account of #22336: Move all core Drupal files under a /core folder to improve usability and upgrades.
If you need help rerolling this patch, you can come to core office hours or ask in #drupal-gitsupport on IRC.
Comment #17
rjgoldsborough CreditAttribution: rjgoldsborough commentedRerolled for d8.
Comment #18
xjmThanks!
Comment #19
tstoecklerI hate to put this to "needs work" again, but there should be a
theme_disable(array('bartik'));
as well in there.Also, in case #1181776: Change theme_default variable to Stark makes it, this is obsolete.
Comment #20
rjgoldsborough CreditAttribution: rjgoldsborough commentedLooks like #1181776: Change theme_default variable to Stark is fixed so marking this as a duplicate. Please feel free to fix if this is the incorrect action to take.
Comment #21
sfyn CreditAttribution: sfyn commentedI am reopening, because I do not understand how making stark the default theme for the minimal install changes this situation - the install profile used for testing is the testing profile, as I understand it.
Comment #22
sun@sfyn: Yes, #1181776: Change theme_default variable to Stark only changed the default theme in core (and the Testing profile) to Stark, but very few tests are using the Testing profile thus far. That last step is a larger challenge and is why the major test rewrite patch in #1373142: Use the Testing profile. Speed up testbot by 50% exists.
Comment #23
sfyn CreditAttribution: sfyn commentedHere is the new patch with the theme disable call from #19
Comment #24
sfyn CreditAttribution: sfyn commentedApologies. I misunderstood the stark issue when I scanned it earlier.