Skip to content
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

Deploy Checklist: Expensify.cash 2021-03-19 #1926

Closed
82 of 85 tasks
OSBotify opened this issue Mar 19, 2021 · 23 comments
Closed
82 of 85 tasks

Deploy Checklist: Expensify.cash 2021-03-19 #1926

OSBotify opened this issue Mar 19, 2021 · 23 comments
Assignees
Labels
🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging StagingDeployCash

Comments

@OSBotify
Copy link
Contributor

OSBotify commented Mar 19, 2021

Release Version: 1.0.16-0
Compare Changes: 1.0.15-0...1.0.16-0

This release contains changes from the following pull requests:

Deploy Blockers:

cc @Expensify/applauseleads

@AndrewGable AndrewGable reopened this Mar 19, 2021
@roryabraham roryabraham added the 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging label Mar 19, 2021
@roryabraham roryabraham added 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging and removed 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging labels Mar 19, 2021
@isagoico isagoico added the 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging label Mar 25, 2021
@isagoico
Copy link

isagoico commented Mar 26, 2021

#1548 cannot be tested because of #1981 (which was a pass) Not sure if it can be checked off @Julesssss or @thienlnam can you guys confirm which is the intended behaviour?

@isagoico
Copy link

isagoico commented Mar 26, 2021

#2032 (comment) Not sure if deploy blocker. Issue is not reproducible in Android devices.

#1948 (comment)

#2010 (comment) - Tested and checked off!

#2040 (comment)

Looks like #2086 was not deployed to staging . It was added to the deploy list after the lock label was applied. Not sure if we should check it off (also looks like internal QA) CC @marcaaron

@Julesssss
Copy link
Contributor

Julesssss commented Mar 26, 2021

#1548 cannot be tested because of #1981 (which was a pass) Not sure if it can be checked off @Julesssss or @thienlnam can you guys confirm which is the intended behaviour?

Hi @isagoico. No need to test #1548, as its test steps were made redundant.

@Julesssss
Copy link
Contributor

I've also commented in #2010 with testing steps. (it's listed twice here, was that a duplication, or is there supposed to be a 4th issue in the list?)

@isagoico
Copy link

Thank a lot ! there was a link missing indeed and I just duplicated the #2010 🤦

@roryabraham
Copy link
Contributor

Looks like #2086 was not deployed to staging . It was added to the deploy list after the lock label was applied.

This was a bug in the deploy process. So we should proceed without that one for this deploy cycle, and try to remember to retest after our next staging deploy.

@roryabraham
Copy link
Contributor

Working with @NikkiWines to determine if #2040 is a true deploy blocker. Looks like that's our last unchecked box. Other PRs are being erroneously added to the list despite not being deployed to staging, but they should be included in the next StagingDeployCash, so we can just ignore them for now. When the new StagingDeployCash is created alongside the production deploy, then we can double-check to make sure any PRs added to this checklist while it was locked are included in the next checklist.

@isagoico isagoico added 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging and removed 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging labels Mar 26, 2021
@roryabraham
Copy link
Contributor

Okay, just a clarification on the process that's happening here:

When the LockCashDeploys label is applied to this issue, it creates a new PATCH version (i.e: bumps from 1.0.6-xx to 1.0.7-0) This is necessary for us to deploy iOS and Android to production. However, on TestFlight that also means that it will be subject to Apple review, and therefore will take ~1 day to deploy. Therefore, on all platforms we should be testing the latest PATCH version (aka 1.0.7-0), but on iOS we'll need to test the highest BUILD version from the previous PATCH version. In this case, that's 1.0.6-5. And in case you're wondering, you can always see a full list of the versions by looking at the Expensify.cash tags here.

As a result, in cases like we had today where there are deploy blockers and we need to remove and re-add the lock label, we won't be able to do staging QA on iOS of the code that was deployed to staging today. So @isagoico that means you can skip iOS staging QA today. We may be able to bypass the Apple review on TestFlight for a small set of people, so hopefully this won't be a problem in the future if we can get you added to that list.

@isagoico
Copy link

Summary of today's run:
Both PRs that required QA were a pass 🎉 I went ahead and checked off #2040 too since the fix was a pass. Only unchecked PR is this one is #2086 that following what was said in QA we should assume it passed QA after this run and we can check it off. (@roryabraham please stop me if I'm wrong)

Issues found during regression testing:
#2121
#2122
#2123 - Deploy blocker
#2124

@roryabraham roryabraham removed the 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging label Mar 29, 2021
@isagoico isagoico added the 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging label Mar 29, 2021
@isagoico
Copy link

@marcaaron
Copy link
Contributor

Hmm it should be testable, but not very obvious so I can test it myself. The two issues are also using more or less the same testing steps.

@marcaaron
Copy link
Contributor

Ah actually I can't see any clear way to test it besides modifying local JS in Web-E. But I did get it working on web staging so I think we can check them off.

Screen Shot 2021-03-29 at 12 10 31 PM

@isagoico
Copy link

Chat Regressions and PRs are finished!
Issues found:

  1. iOS/Android - Profile page does not scroll  #2147
  2. Android - Profile - "Save" button overlaps on the self select pronouns field #2149
  3. [HOLD] Going back to main list after keyboard call won't close keypad #2150

PRs are finished too, no comments added.

@isagoico isagoico added 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging and removed 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging labels Mar 30, 2021
@isagoico
Copy link

@roryabraham Regression is done! iOS build in TF was the same as yesterday (1.0.7-0) so we holded on executing the regression on that one. Let me know if we should execute either way.

@isagoico isagoico removed the 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging label Mar 31, 2021
@roryabraham
Copy link
Contributor

roryabraham commented Mar 31, 2021

Nope, for the time being that's the plan! No need to perform regression testing twice on the same app version.

@isagoico isagoico added the 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging label Mar 31, 2021
@isagoico
Copy link

isagoico commented Mar 31, 2021

Regression is finished!
3 issues found today:

  1. Group Creation - Message that you reached the max participants is not displayed.  #2175 - Deploy Blocker
  2. Web - Email Test - The username on the left hand navigation isn't displayed bold when a new message arrives #2177
  3. Android - No notifications are received when app is in the background #2184 - Deploy Blocker
  • iOS in TF is still on build 1.0.7-0 so we skipped regression on this round. Hopefully TF is all set up for tomorrow so we can resume iOS testing 🤞

Today's PRs were all a pass 🎉

@Julesssss there's this PR #2110 that I think it's internal QA. Can you confirm?

Removing the lock label.

@isagoico isagoico removed the 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging label Mar 31, 2021
@Julesssss
Copy link
Contributor

Hi @isagoico. Yeah that can be tested internally as the test steps are a bit tricky currently.

@isagoico isagoico added the 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging label Apr 1, 2021
@marcaaron
Copy link
Contributor

Fix for 2175 in review now #2189

@isagoico
Copy link

isagoico commented Apr 1, 2021

Regression is finished!
1 issue found:

  1. Android - Chat - Tapping plus opens chat instead of new or group chat options #2207 - Deploy blockers

PRs are finished too.
2 comments added:

  1. Add Video Call Chat Links #1878 (comment) - Checking it off.
  2. Fix sign in page styles #2192 (comment)

@isagoico isagoico added 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging and removed 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging labels Apr 2, 2021
@isagoico
Copy link

isagoico commented Apr 6, 2021

@isagoico isagoico added 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging and removed 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging labels Apr 6, 2021
@isagoico isagoico removed the 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging label Apr 7, 2021
@roryabraham roryabraham added 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging and removed 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging labels Apr 7, 2021
@isagoico
Copy link

isagoico commented Apr 7, 2021

We have been able to reproduce this issue several times and in different devices during regression 1.0.1-15 https://github.com/Expensify/Expensify/issues/157735. It's not consistently reproducible.

@isagoico
Copy link

isagoico commented Apr 7, 2021

Regression is finished!
3 issues found today:

  1. Web - Login - Blank white screen after login #2278 - Possible deploy blocker (?)
  2. iOS/Android - Message - Copy message menu is not displayed when pressing on the message #2279
  3. Android - Chat - Recent users displayed without user's name #2280

PRs are finished too!
No comments added 🎉

#2110 was going to be tested internally CC @Julesssss
#2050 is missing testing steps

@isagoico isagoico added 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging and removed 🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging labels Apr 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔐 LockCashDeploys 🔐 Prevent new code from being deployed to staging StagingDeployCash
Projects
None yet
Development

No branches or pull requests

7 participants