-
Notifications
You must be signed in to change notification settings - Fork 184
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
[tests-only][full-ci] make user enable disable feature use graphapi #6790
Conversation
64559ae
to
b9c21e7
Compare
tests/acceptance/features/coreApiWebdavOperations/refuseAccess.feature
Outdated
Show resolved
Hide resolved
tests/acceptance/features/coreApiWebdavOperations/refuseAccess.feature
Outdated
Show resolved
Hide resolved
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.
this test runs in reva. so need to find better way
tests/acceptance/features/coreApiWebdavOperations/refuseAccess.feature
Outdated
Show resolved
Hide resolved
170bc41
to
9c8b661
Compare
88c19f6
to
1f312b0
Compare
...s/acceptance/features/coreApiShareCreateSpecialToShares2/createShareWithDisabledUser.feature
Outdated
Show resolved
Hide resolved
668b828
to
55090a2
Compare
55090a2
to
77dee2c
Compare
2a6b282
to
bdfa438
Compare
bdfa438
to
fd61ba5
Compare
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.
LGTM
Kudos, SonarCloud Quality Gate passed! |
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.
LGTM 👍
...s/acceptance/features/coreApiShareCreateSpecialToShares2/createShareWithDisabledUser.feature
Show resolved
Hide resolved
…6790) * make user enable disable feature use graphapi * change the step definition code for user disable action * updated step definition code for user disable feature * updated user disable implementation * corrected the error of step implementation code
…6790) * make user enable disable feature use graphapi * change the step definition code for user disable action * updated step definition code for user disable feature * updated user disable implementation * corrected the error of step implementation code
…6790) * make user enable disable feature use graphapi * change the step definition code for user disable action * updated step definition code for user disable feature * updated user disable implementation * corrected the error of step implementation code
…6790) * make user enable disable feature use graphapi * change the step definition code for user disable action * updated step definition code for user disable feature * updated user disable implementation * corrected the error of step implementation code
Description
The steps where admin disable any user issue were marked failed as it uses OCS API. At present, this task couldn't be done using ocs API as the curl request to that endpoint results in an error. This PR redacted that step so that the feature now uses graph API and the Scenario gets passed and they were removed from the expected failure file.
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: