Problem/Motivation
Code style cleanup, tugboat, gitlab CI & basic Tests
Same as last year, James?
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork drowl_admin_dashboard-3571234
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
lrwebks commentedSame procedure as every year!
Comment #3
lrwebks commentedNow that I think about it, I will probably do the other issues assigned to me first, so that the "spit-shine" is only applied at the end here.
Comment #5
lrwebks commentedUnfortunately I cannot fix the whole pipeline here, since Stylelint especially wants to unwrap and modify the minified CSS files for some reason, which is probably unwanted, right? Also, what features should be tested here specifically? I can and will attach the
GenericModuleTestBasefor premade Drupal installation, settings, etc. tests, but what else?Comment #6
lrwebks commentedA bit messy here right now, which does bother me, but I have wasted enough time here already and don't seem to get any further with this...
Comment #7
lrwebks commented@anybody and I talked about what basic tests to also include here, so I will do that.
Comment #8
lrwebks commentedI have added the tests as I envision them. Unfortunately I cannot test them locally since the schema errors present in the view configs apparently take higher precedence in PHPUnit. I don't really understand these errors and I fear just deleting the config that causes the errors might break the config that was intended.
Comment #9
anybodyTests have phpcs errors
Comment #10
anybodyRegarding the tests it looks like the image module dependency was missing in the .info.yml
Comment #11
anybodyMaybe moving the views to config/optional is good enough. Otherwise we'll need to add 'test_user_config' to $modules.
Comment #12
anybodyOkay solved, now the tests seem indeed wrong.
Comment #13
anybody@lrwebks:
Please test:
Current tests seem a bit strange partially, especially the redirect for users without permission to the dashboard don't make much sense to me. Assume that users either have both or none of the permissions logically.
Comment #14
lrwebks commentedComment #15
anybodyComment #16
anybodyAll green, thanks @lrwebks!! :)