Needs work
Project:
Legal
Version:
3.0.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 May 2024 at 13:32 UTC
Updated:
14 Sep 2024 at 15:46 UTC
Jump to comment: Most recent
This is a follow-up issue of #3074688: Password can not be reset, when user hasn't accepted the legal terms yet, where we didn't finish the required tests for the feature.
Furthermore, there are a few old tests using legacy themes, which is the reason the testing pipeline currently fails.
Fix, comment in and add tests for "Password can not be reset, when user hasn't accepted the legal terms yet"
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
grevil commentedComment #3
grevil commentedEDIT: Wrong issue
Comment #4
grevil commentedThrough adjusting the tests I found a regression caused by #3414370: Reset notice is showing up twice (from core and legal module) and don't disappear after password change. I commented out the part of the test, that let them fail for now. We should comment them in again through #3447367: The one-time login message is not displayed anymore, when the user is first redirected to the T&C page..
Comment #6
grevil commentedComment #7
robert castelo commented@Grevil I fixed this already, but let me know if there's anything from this branch you think should be merged in.
Comment #8
grevil commentedOne test still fails in 3.0.x: https://git.drupalcode.org/project/legal/-/jobs/1603633
Had similar issues yesterday, where locally running the tests everything went green, but on remote one fails.
I'll rebase the branch on 3.0.x, try to fix the test and readd the "testPasswordResetLegalAcceptOnEveryLogin()" test.
Comment #9
grevil commentedOk, no idea why they are failing on remote. The new test throws the same exact error as the "testPasswordResetWithoutLegalAccepted()" test in the 3.0.x phpunit job:
The "pass-reset-token" is not even included in the URL for some reason... locally the tests just run fine.
Comment #10
grevil commented@Robert Castelo maybe you have any further ideas? I'd be fine with a new release, as all tests are passing locally, but this test behavior is still quite confusing.
Comment #11
robert castelo commented@Grevil maybe something in the .gitlab-ci.yml file?
What else is different between local and Gitlab environments.
Comment #12
robert castelo commentedI'm going to do thorough manual testing this week and planning to do a Legal 3.0.2 release next weekend.