-
Notifications
You must be signed in to change notification settings - Fork 210
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
cleanup(auth, content): Remove feature flags for reset password with code #17672
Conversation
4df1924
to
56b6a6d
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.
Thank you @vpomerleau for the test cleanup :) but we would have to skip the sync tests for chromium browser (comments inline) as so far they were being skipped by the config set up but once the cleanup is merged they will start running and fail for chromium in nightly.
const config = await configPage.getConfig(); | ||
test.skip( | ||
config.featureFlags.resetPasswordWithCode !== true, | ||
'see FXA-9728, remove conditional skip when feature flag removed' |
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.
For the sync tests we would have to skip the tests for Chromium otherwise it will fail in Nightly. Please see (#17665)
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.
These tests have been running for a few months, resetPasswordWithCode
is set to true in all environments. If we need to skip these tests, we would also need to look at all of the other syncV3 tests that are not skipped for chromium, as far as I can tell?
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.
Oh. I thought the resetPassword/resetPasswordWithLink/syncV3resetPassword.spec.ts
was being skipped in the past. But if it was always set to true then it would be probably fine.
I found this with the recent nightly run for chromium tests: https://app.circleci.com/pipelines/github/mozilla/fxa/54464/workflows/e26432fd-2d64-4740-a41d-3ee2e2275b02/jobs/530856/parallel-runs/4?filterBy=ALL
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.
ah, you already removed the resetPasswordWithLink
test so it wouldn't matter. Sorry for the confusion. 😿
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.
All good, thank you for the review! I did indeed remove all the skipped resetPasswordWithLink
tests.
I'm uncertain when tests need to be skipped in Chromium for sync - looks like it's only two tests at the moment, which seems surprising (= I would expect more tests to fail)
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.
👍 Thank you. Less code FTW.
Because: * Reset password with code is now fully rolled out This commit: * Remove functional tests for reset password with link * Remove config check for resetPasswordWithCode flag in functional-tests * Remove content-server resetPasswordWithCode feature flag/env * Remove auth-server passwordForgotOtp.enabled config Closes #FXA-9728, FXA-10387
56b6a6d
to
f3dd501
Compare
Because
This pull request
Issue that this pull request solves
Closes: #FXA-9728, FXA-10387
Checklist
Put an
x
in the boxes that applyScreenshots (Optional)
Please attach the screenshots of the changes made in case of change in user interface.
Other information (Optional)
Companion PRs for SRE: