-
Notifications
You must be signed in to change notification settings - Fork 6
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
Test Results for 2.0.1 release #139
Comments
Testing functionality0 No special password requirements / no link expiration requirementsThese tests make sure the app does not block anything if all its settings are disabled
|
1 Minimum characters requiredTest Setup:
|
2 Lowercase letters requiredTest Setup:
3 Uppercase letters requiredTest Setup:
|
4 Numerals requiredTest Setup:
|
5 Special characters requiredTest Setup:
Note: issue #41 is still outstanding. You can check "Restrict to these special characters" and leave the list empty. Effectively the "check" makes no difference. |
6. Public Link expiration
|
7. User Password policies
|
8. Force change on first login
|
9 Number of last passwords that should not be used
Issue #57 is fixed. |
Using occ command to expire passwords.
The above passes with the code fixes in PR #144 - ref issue #143 for what was going slightly wrong. That PR has been merged - good. |
Issue #53 Password History is cleaned up:
Works. Notifications are cleaned up: |
@phil-davis enough for Oracle, yes |
I realised that we can easily run the current automated acceptance tests on Oracle - PR #145 demonstrates that it passes. So we know Oracle is OK at least for the parts automated so far. (this is another advantage of automation - components can be switched in/out and automated tests can verify behaviour) |
Tarball checks out OK |
Test Plan Password policy
Areas to test
1. web UI
1.1 admin creates a user
1.2 admin changes password of a user
1.3 user changes own password in personal user settings
1.4 user sets own password on lost password page
1.5 user creates a public share (this is using the share API, so no need to test by itself if the share API is tested)
2. User Provisioning API
2.1 users / adduser
2.2 users / edituser
3. share API
3.1 create a new share
3.2 update share
4. occ
4.1 user:add
4.2 user:resetpassword
5. guests app
The text was updated successfully, but these errors were encountered: