Acceptance tests for resetting user passwords with the provisioning API - #32749
Merged
Conversation
Contributor
Author
|
Backport |
individual-it
approved these changes
Sep 18, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Add acceptance test steps that reset a user password using the provisioning API.
Add test scenarios to check what admin, sub-admin and ordinary users can and cannot do to reset passwords with the provisioning API.
Motivation and Context
I want to do various user password resets from password_policy tests,
but such tests do not exist in core yet.
How Has This Been Tested?
Local run of the new acceptance test feature files.
Types of changes
Checklist:
Open tasks: