New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG Prevent password validator min score producing false negatives #8013
BUG Prevent password validator min score producing false negatives #8013
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a great change to me!
OK - I assume this is a bug in 4.0 as well as 4.1, can we target 4.0 whilst it's still a supported version? |
Actually 4.0 is safe; We'd refactored PasswordValidator in 4.1, introducing the bug there. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this is better than it used to be, I don't think it addresses the fundamental problem that you have TestNames disjointed from Tests.
Althought it might not be possible to address this without doing breaking changes. So it might have to wait until SS5.
Yeah after I looked at this I realised my error. One is the list of all available tests, the other is the list of all enabled tests. The reason they are separate was correct and intentional. |
@dhensby Are you happy to merge this? |
I am, but does it fully address the initial bug? |
Replaces #7995
Fixes min score failing if no tests are set
Fixes min score failing if there are no failing tests
Adds unit tests to cover the above
Fix up bad phpdoc, code style, linting, and upgrade deprecated API usage