LG-6193: Enable personal key step in development environment#6229
Merged
LG-6193: Enable personal key step in development environment#6229
Conversation
6a2850f to
a736ed5
Compare
aduth
commented
Apr 22, 2022
e89a7c0 to
0660117
Compare
0660117 to
c1e1bff
Compare
This was referenced Apr 26, 2022
ee6e7b5 to
b3fe794
Compare
aduth
commented
Apr 28, 2022
| gem 'aws-sdk-cloudwatchlogs', require: false | ||
| gem 'brakeman', require: false | ||
| gem 'bullet', '>= 6.0.2' | ||
| gem 'capybara-webmock', git: 'https://github.com/hashrocket/capybara-webmock.git', ref: '63d790a0' |
Contributor
Author
There was a problem hiding this comment.
The reason this points to git is because there are unpublished changes that we need.
Specifically: hashrocket/capybara-webmock@f3d27b1
ef938e8 to
a9211e3
Compare
a9211e3 to
8be2414
Compare
This was referenced Apr 28, 2022
8be2414 to
9fb2a18
Compare
aduth
added a commit
that referenced
this pull request
May 2, 2022
…enderer **Why**: Because the current implementation relies on the assumption that we would only ever want to show "Submit" as the label of the last button in the flow, which is not the intention, and is not compatible with the current implementation of the personal key confirmation modal in the IdV API React implementation. Related discussion: #6229 (comment) changelog: Upcoming Features, Identity Verification, Add personal key step screen
aduth
added a commit
that referenced
this pull request
May 2, 2022
…enderer (#6280) * Update FormStepsButton to place choice of "Submit" or "Continue" to renderer **Why**: Because the current implementation relies on the assumption that we would only ever want to show "Submit" as the label of the last button in the flow, which is not the intention, and is not compatible with the current implementation of the personal key confirmation modal in the IdV API React implementation. Related discussion: #6229 (comment) changelog: Upcoming Features, Identity Verification, Add personal key step screen * Fix spec lingering reference to personal key confirm "Submit"
9fb2a18 to
cd982e9
Compare
peggles2
pushed a commit
that referenced
this pull request
May 3, 2022
…enderer (#6280) * Update FormStepsButton to place choice of "Submit" or "Continue" to renderer **Why**: Because the current implementation relies on the assumption that we would only ever want to show "Submit" as the label of the last button in the flow, which is not the intention, and is not compatible with the current implementation of the personal key confirmation modal in the IdV API React implementation. Related discussion: #6229 (comment) changelog: Upcoming Features, Identity Verification, Add personal key step screen * Fix spec lingering reference to personal key confirm "Submit"
Presumably we relied previously on PII being false in most cases. A handful of tests create a profile without a valid user attached to it, so now that we're assigning default PII for profiles, we should also only actually encrypt it if there's a valid user
In 259c213 we're now reliably setting default_url_options so that the URL will be generated correctly and we don't have to test path
too many tests assume it won't be there (probably a problem worth resolving)
Selenium::WebDriver::Error::ElementNotInteractableError:
element not interactable
Capybara::NotSupportedByDriverError:
Capybara::Driver::Base#response_headers
shouldn't redirect if invalid CSP target?
changelog: Upcoming Features, Identity Verification, Add personal key step screen
So that they're enabled in test
JS browser would not have visibility to content otherwise
Co-authored-by: Zach Margolis <zachmargolis@users.noreply.github.com>
When JS is enabled, previous step triggers spinner button, and there may be a brief delay before review step is shown. Avoid spec flakiness by allowing some wait for the review path to be shown. precedent: https://github.com/18F/identity-idp/blob/e7501424b59f887aa12bd255f69de03502969fa0/spec/features/idv/proofing_components_spec.rb#L25
So that tests run against the in-production version, but we re-run personal key pages with both side of the toggle
Because it's a spinner button, we need to be able to wait for navigation to complete
00ff8cc to
15cfc45
Compare
This was referenced May 11, 2022
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why: So that a user can functionally complete the proofing process using the new IdV app.
Testing Instructions:
Implementation Notes:
Screenshot: