Skip to content

Deploy to the qa environment#1537

Closed
gemfarmer wants to merge 44 commits intostages/qafrom
stages/bsh-2017-07-10
Closed

Deploy to the qa environment#1537
gemfarmer wants to merge 44 commits intostages/qafrom
stages/bsh-2017-07-10

Conversation

@gemfarmer
Copy link
Contributor

@gemfarmer gemfarmer commented Jul 11, 2017

This PR deploys changes made in Sprint 35 to the qa environment.

A lot happened this sprint. Changes include:

el-mapache and others added 30 commits June 27, 2017 16:37
**Why**: The feature in question is account reactivation, this improves
naming consistency
**Why**: Consistency is key. In this case, the cancel link on the
forgot password page was always linking to the home page.

**How**: Don't use the `shared/cancel` partial because the user will
never be signing up or going through IdV if they are accessing the
Forgot Password page, so we can directly link to the decorated session's
`cancel_link_path` which contains the logic to determine whether it
should point to the home page or the branded page.
**Why**: Testing for the link text alone is not enough. We also
want to make sure the link is pointing to the right place.
Renames account recovery to account reactivation
Return to branded page consistently when canceling
**Why**:
Removing references to the session will make it easier to
extract VendorValidator work into a background job
**Why**:
Extracting this into a serializable object will make it
easier to refactor these classes into background jobs.
**Why**: We were comparing datetimes without freezing Time.zone.now,
leading to flickering specs.

**How**: Instead of comparing `otp_last_sent_at` with the current time,
check that the current `otp_last_sent_at` is greater than the previous
one.
**Why**: To enable rollout
Make otp_rate_limiter_spec more robust
**Why**: The retry and raise portion of `find_or_create_with_phone`
was not tested.
**Why**:
This tells the screen reader the content in this div
is hidden. When the accordian is expanded, aria-
hidden is changed to false, letting the screen
reader know there is new content on screen.
Improve test coverage for OtpRequestsTracker
**Why**
The situation

As @andrewhughey had stated in 18F/identity-private#1890 (comment), here is the flow that this PR is fixing:

create account (email, password, 2FA)
verify identity (person info, financial info)
choose to confirm address by mail
send letter
see profile / flash message that letter was sent
sign out
sign in
asked for code from letter but oh no! I never got a letter
choose send new letter

expected: send new letter screen

actual: restart identity verification

**How**

This PR adds logic to prevent the user from being redirected back to identity verification, sending them to the "Send another letter" confirmation screen instead, as expected.

The faulty redirect was happening because the a request to send more mail was triggering the IdvSession service, which redirects to verification if verification hasn't been completed. To fix this, we added an exception that prevents that redirect if a user has mail already sent mail.

For issue: 18F/identity-private#1890
**Why**: As part of backgrounding vendor proofing, it will be helpful
for the IdV form objects to behave like the rest of the form objects in
the app so we can extract them from the `Idv::Step` subclasses and
invoke them in the controller.
Add aria-hidden to accordian content div
Return FormResponse from IdV form submission
Prevent Verify by mail flow redirect bug
Add CBP GOES production config
**Why**: Our test print had issues with unicode
Send plain ASCII attributes in verify-by-mail
**Why**: Helps with our translation pipeline

**How**: Make sure keys use word characters and underscores only
**Why**:
This will let us break submission in to two steps and
into two controller actions which will further help us
when we move the call to our vendors to background
jobs.
Separate idv_form from Idv::Step classes
zachmargolis and others added 14 commits July 3, 2017 14:24
**Why**: Results back from vendor
**Why**: To support a more complete localization
**Why**:
ERBs are compiled once, so they're stuck with whatever locale they
are compiled in. This makes one .js with all translated keys for all
locales that can be cached, and then looks up the locale from the
<html lang> attribute on every page.
**Why**: For consistency with the behavior during account creation
cancellation.

**How**:
- Add a new controller and route for signing the user out without having
to go through `SamlIdpController#logout` since there is no single logout
to be performed in this scenario
- Replace the URL of the Cancel link to point to this new route
**Why**: For a consistently localized experience
Return to branded page when canceling sign in
Update translated JS to use locale dynamically from HTML
**Why**: One last small refactor step before making the job async
Extract a synchronous proofing job
Use CBP TTP logo for GOES SPs
@gemfarmer gemfarmer requested a review from monfresh July 11, 2017 15:38
@zachmargolis
Copy link
Contributor

For lower envs like this we can just push the SHA directly ot the stages/qa tag, no need to generate a merge commit like this

@monfresh
Copy link
Contributor

I'd like to wait to merge the latest Equifax fixes please, so we can resume testing on staging. Otherwise, we'll have to wait until the next release cycle.

@gemfarmer
Copy link
Contributor Author

@zachmargolis ah! Good to know. Which environments do I need to submit a formal PR for?

And yes, I can wait for the Equifax fixes to roll in @monfresh. Let me know when those are ready for deployment!

@monfresh
Copy link
Contributor

@gemfarmer PR only needed for staging

@monfresh
Copy link
Contributor

@gemfarmer All set. The equifax changes have been merged. Please close this PR, and follow the instructions here:
https://github.com/18F/identity-private/wiki/Release-Management#create-a-release-candidate-branch-and-push-it-to-github
Note that the branch name must begin with rc, not your initials.

@monfresh
Copy link
Contributor

Also, the branch name must be based on the date of the release to production, which is July 24, not the 10th.

@gemfarmer gemfarmer closed this Jul 11, 2017
@gemfarmer gemfarmer deleted the stages/bsh-2017-07-10 branch July 11, 2017 19:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants