This seems fine, but I don't see any mention of inverse tests in the test plan. Are we sure that password changes will continue to fail in scenarios where it is expected to fail, such as in admin password incorrect and user not authorized cases? If there are already automated tests that exercise the code being changed and verify these scenarios then that's fine. If not, then please add such tests to the test plan.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728031 Title: [SRU] Unable to change user password when ENFORCE_PASSWORD_CHECK is True To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1728031/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
