[NoQA] e2e: record `messageSent` interaction #43302

kirillzyusko · 2024-06-07T15:13:40Z

To Do

The original test is flaky one, so it has to fixed before merging this PR.

Details

Should be merged after #43178

Fixed Issues

$ #35225
PROPOSAL: #35225 (comment)

Tests

Run e2e pipeline and be sure it's green

Offline tests

N/A

QA Steps

N/A

PR Author Checklist

I linked the correct issue in the ### Fixed Issues section above
I wrote clear testing steps that cover the changes made in this PR
- I added steps for local testing in the Tests section
- I added steps for the expected offline behavior in the Offline steps section
- I added steps for Staging and/or Production testing in the QA steps section
- I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
- I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
I included screenshots or videos for tests on all platforms
I ran the tests on all platforms & verified they passed on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
I followed proper code patterns (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  - If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I followed the guidelines as stated in the Review Guidelines
I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
I verified that if a function's arguments changed that all usages have also been updated correctly
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

melvin-bot · 2024-06-07T15:13:45Z

@Pujan92 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

perunt · 2024-06-10T10:55:10Z

src/pages/home/report/comment/TextCommentFragment.tsx

@@ -48,6 +49,10 @@ function TextCommentFragment({fragment, styleAsDeleted, styleAsMuted = false, so
    const {translate} = useLocalize();
    const {isSmallScreenWidth} = useWindowDimensions();

+    useEffect(() => {
+        Performance.markEnd(CONST.TIMING.MESSAGE_SENT, {message: text});


I'm just curious if we need to measure it after each text change or if it should be used only once

Well, basically this effect will be called every time (i. e. for each text message), but since there is no corresponding start event -> such measurements will be ignored. And we'll get measurements only for associated end/start events with the same text/message. I hope I answered on the question 😅

mountiny

Thanks!

mountiny · 2024-06-17T11:38:10Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

hannojg · 2024-06-26T10:29:45Z

We want to check if the network caching is working correctly when sending a message. We will send an actual message to the server during the warmup phase of the test, but on subsequent runs where we use the network cache we shouldn't send a real request to the server. Let's make sure it works correctly!

mountiny · 2024-06-26T11:51:33Z

@kirillzyusko Sorry, there are conflicts now.

Is this ready to be merged or you need to address the comment from Hanno first?

kirillzyusko · 2024-06-26T11:54:24Z

Is this ready to be merged or you need to address the comment from Hanno first?

@mountiny Yeah, I need to check that first 👍

mountiny · 2024-06-28T11:52:20Z

@kirillzyusko ping me in slack when this is ready, thank you!

kirillzyusko · 2024-08-20T08:30:39Z

@hannojg I resolved all merge conflicts - would you mind to have a look? 👀

kirillzyusko · 2024-08-20T10:50:47Z

We want to check if the network caching is working correctly when sending a message. We will send an actual message to the server during the warmup phase of the test, but on subsequent runs where we use the network cache we shouldn't send a real request to the server. Let's make sure it works correctly!

@hannojg I verified and adjusted the code to match this requirement! The PR is ready for a review!

mountiny

LGTM @hannojg did you want to give this one a review?

hannojg

As internally discussed: LGTM!!

OSBotify · 2024-08-23T04:20:40Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2024-08-26T23:17:51Z

🚀 Deployed to staging by https://github.com/mountiny in version: 9.0.25-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	failure ❌
🕸 web 🕸	success ✅

OSBotify · 2024-08-27T00:08:13Z

🚀 Deployed to staging by https://github.com/mountiny in version: 9.0.25-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	failure ❌
🕸 web 🕸	success ✅

kirillzyusko requested a review from a team as a code owner June 7, 2024 15:13

melvin-bot bot removed the request for review from a team June 7, 2024 15:13

melvin-bot bot requested a review from Pujan92 June 7, 2024 15:13

perunt approved these changes Jun 10, 2024

View reviewed changes

kirillzyusko added 3 commits June 17, 2024 11:01

e2e: record message_sent interaction

b45399d

fix: eslint

f3ae4d6

fix: prettier

06f87b3

kirillzyusko force-pushed the e2e/message-sent-interaction branch from 585bdf4 to 06f87b3 Compare June 17, 2024 08:01

mountiny assigned kirillzyusko Jun 17, 2024

mountiny self-requested a review June 17, 2024 11:00

Merge branch 'main' into e2e/message-sent-interaction

b92fb23

mountiny previously approved these changes Jun 17, 2024

View reviewed changes

kirillzyusko changed the title ~~[NoQA] e2e: record messageSent interaction~~ [HOLD] [NoQA] e2e: record messageSent interaction Jun 17, 2024

kirillzyusko changed the title ~~[HOLD] [NoQA] e2e: record messageSent interaction~~ [NoQA] e2e: record messageSent interaction Jun 26, 2024

Merge branch 'main' into e2e/message-sent-interaction

97972cb

kirillzyusko dismissed mountiny’s stale review via 97972cb August 19, 2024 11:59

kirillzyusko added 2 commits August 19, 2024 15:14

fix: eslint

0ebe2cd

fix: actually make tests runnable

8143c8d

fix: send real message only during warmup stage

88c4b22

mountiny approved these changes Aug 21, 2024

View reviewed changes

hannojg approved these changes Aug 22, 2024

View reviewed changes

mountiny merged commit 156f0a2 into Expensify:main Aug 23, 2024
17 checks passed

github-actions bot mentioned this pull request Aug 26, 2024

Deploy Checklist: New Expensify 2024-08-26 #48035

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[NoQA] e2e: record `messageSent` interaction #43302

[NoQA] e2e: record `messageSent` interaction #43302

kirillzyusko commented Jun 7, 2024 •

edited

Loading

melvin-bot bot commented Jun 7, 2024

perunt Jun 10, 2024

kirillzyusko Jun 10, 2024

mountiny left a comment

mountiny commented Jun 17, 2024 •

edited

Loading

hannojg commented Jun 26, 2024

mountiny commented Jun 26, 2024

kirillzyusko commented Jun 26, 2024

mountiny commented Jun 28, 2024

kirillzyusko commented Aug 20, 2024

kirillzyusko commented Aug 20, 2024

mountiny left a comment

hannojg left a comment

OSBotify commented Aug 23, 2024

OSBotify commented Aug 26, 2024

OSBotify commented Aug 27, 2024

[NoQA] e2e: record messageSent interaction #43302

[NoQA] e2e: record messageSent interaction #43302

Conversation

kirillzyusko commented Jun 7, 2024 • edited Loading

To Do

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Jun 7, 2024

perunt Jun 10, 2024

Choose a reason for hiding this comment

kirillzyusko Jun 10, 2024

Choose a reason for hiding this comment

mountiny left a comment

Choose a reason for hiding this comment

mountiny commented Jun 17, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

hannojg commented Jun 26, 2024

mountiny commented Jun 26, 2024

kirillzyusko commented Jun 26, 2024

mountiny commented Jun 28, 2024

kirillzyusko commented Aug 20, 2024

kirillzyusko commented Aug 20, 2024

mountiny left a comment

Choose a reason for hiding this comment

hannojg left a comment

Choose a reason for hiding this comment

OSBotify commented Aug 23, 2024

OSBotify commented Aug 26, 2024

OSBotify commented Aug 27, 2024

[NoQA] e2e: record `messageSent` interaction #43302

[NoQA] e2e: record `messageSent` interaction #43302

kirillzyusko commented Jun 7, 2024 •

edited

Loading

mountiny commented Jun 17, 2024 •

edited

Loading