-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Allow QA to test the Fullstory integration in staging #51211
Comments
Whoops! This issue is 2 days overdue. Let's get this updated quick! |
6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
@danieldoglas I was wondering if this is all simple as adding a user email check to the same place where we make sure to only start a FS session if the environment is production? |
Huh... This is 4 days overdue. Who can take care of this? |
Discussed a solution here |
awaiting the decision about the email. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.58-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-11-14. 🎊 |
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
@danieldoglas Eep! 4 days overdue now. Issues have feelings too... |
There's no payment on this one. |
assigning @anmurali so she can work on writing the tests we want here. |
WIP |
@danieldoglas, @anmurali Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@danieldoglas, @anmurali Eep! 4 days overdue now. Issues have feelings too... |
@danieldoglas, @anmurali 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it! |
@danieldoglas, @anmurali 10 days overdue. I'm getting more depressed than Marvin. |
Regression test proposal
Repeat the above steps by signing up on new.expensify.com Repeat the above steps by signing in with a previously signed up [email protected] on www.expensify.com, new.expensify.com). For sign in, verify the additional step below as well: Repeat the above steps including step 8 with a previously signed up (and redirected to new dot) [email protected] on hybrid app (iOS and Android) |
This is all setup! |
Problem: Our FullStory integration is quickly becoming a critical part of New Expensify. If it breaks than we are left blind without the ability to debug issues for users and determine the usability of New Expensify.
Solution: Add a FullStory test case for Applause to test on each staging build to verify that we haven’t added any regressions to the integration. We need to be able to record sessions for specific accounts on staging, but keep the integration turned off for staging to not hit our session limit.
Issue Owner
Current Issue Owner: @anmuraliThe text was updated successfully, but these errors were encountered: