#51180 Issue: 50860 - Port Password Policy test cases from TET to python3 final
Closed by spichugi. Opened by aborah.
aborah/389-ds-base pass_policy_final  into  master

Download 51180.patch

Bug Description: Port Password Policy test cases from TET to python3 final

Relates/Fixes: https://pagure.io/389-ds-base/issue/50860

Author: aborah

Reviewed by: ???

The value is not unique

In other test cases, you specify what kind of failure it is. I think it's better when it's consistent

These two lines are very strange... Why is it done like this?

1 new commit added

  • Fixing Simon's comments

The value is not unique

Corrected

In other test cases, you specify what kind of failure it is. I think it's better when it's consistent

Corrected

These two lines are very strange... Why is it done like this?

Corrected

LGTM! Ack

rebased onto df06a881ebde32a89c29bbb8e5405dc8a30411ba

rebased onto fe098d95c94061c299aceb0d117489a7217029d9

rebased onto 8b8bc238979e9a0bf7fbc63a9f2c643bf452c27c

1 new commit added

  • Issue: 50860 - Port Password Policy test cases from TET to python3 final

2 new commits added

  • Issue: 50860 - Port Password Policy test cases from TET to python3 final
  • Issue: 50860 - Port Password Policy test cases from TET to python3 final

2 new commits added

  • Issue: 50860 - Port Password Policy test cases from TET to python3 final1
  • Issue: 50860 - Port Password Policy test cases from TET to python3 final

rebased onto 4fce7b5fa1c2cb48b090bdc40e62fe361aafb15a

1 new commit added

  • Real one

Pull-Request has been closed by aborah

Pull-Request has been reopened by vashirov

rebased onto d4f5dce72686fb5753fa05f3b888426edaa175a4

rebased onto d4f5dce72686fb5753fa05f3b888426edaa175a4

Pull-Request has been merged by vashirov

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/4233

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.

Pull-Request has been closed by spichugi

Metadata