[No QA] [HOLD] Integration Errors Revamp Testing by stephanieelliott · Pull Request #83106 · Expensify/App

stephanieelliott · 2026-02-20T20:29:45Z

Explanation of Change

Creates .MD files integration error messages

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/469226
PROPOSAL: N/A

Tests

Verify that no errors appear in the JS console

Offline tests

QA Steps

N/A, no tests

Verify that no errors appear in the JS console

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
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 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 used JaimeGPT to get English > Spanish translation. I then posted it 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.ts 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 new assets were added or existing ones were modified, I verified that:
- The assets are optimized and compressed (for SVG files, run npm run compress-svg)
- The assets load correctly across all supported platforms.
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.
I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
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.mp4

Android: mWeb Chrome

android.mweb.mp4

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

web.mp4

OSBotify · 2026-02-20T20:33:36Z

Your New Help changes have been deployed to https://209684f8.newhelp.pages.dev ⚡️

stephanieelliott · 2026-02-20T21:13:25Z

@CortneyOfstad the folders have been added on this branch!

Here is where you can find them to add articles:
Docs > Articles > new-expensify/expensify-classic > connections > [integration name] > troubleshooting (folder) > [subfolder]

- Troubleshooting.html and subsections (Authentication-and-Login-errors, Connection-errors, Export-Errors, Sync-Errors) so Classic NetSuite error articles are reachable from the help site. Part of Integration Errors Revamp (splitting PR #83106). Made-with: Cursor

- Articles: Authentication-and-Login-errors, Connection-errors, Export-Errors, Sync-Errors, NetSuite-FAQ (90 articles). - Hub pages: Troubleshooting and subsection hubs so articles are reachable from the help site. Part of Integration Errors Revamp (splitting PR #83106). Made-with: Cursor

- Expensify Classic: Certinia articles (Auth, Export, Sync errors, FAQ). - Expensify Classic: add Sync-Errors hub page for Certinia so Sync-Errors articles are reachable (Auth and Export hubs already on main). Part of Integration Errors Revamp (splitting PR #83106). Made-with: Cursor

…y Classic) - New Expensify: articles for Auth, Connection, Export, Sync errors, FAQ, plus root Configure/Connect/Troubleshooting. Removed placeholder files. - Expensify Classic: same structure and error articles. - Hub pages for both already exist on main. Part of Integration Errors Revamp (splitting PR #83106). Made-with: Cursor

- Root: Configure, Connect, Troubleshooting. - Troubleshooting: Auth, Connection, Export, Sync errors, FAQ. - Hub pages already exist on main. Part of Integration Errors Revamp (splitting PR #83106). Made-with: Cursor

- Root: Configure, Connect, Xero-Troubleshooting. - Troubleshooting: Auth, Connection, Export, Sync errors, FAQ. - Hub pages already exist on main. Part of Integration Errors Revamp (splitting PR #83106). Made-with: Cursor

- Articles: Authentication-and-Login-errors, Connection-errors, Export-Errors, Sync-Errors, NetSuite-FAQ (90 articles). - Hub pages: Troubleshooting and subsection hubs so articles are reachable from the help site. Part of Integration Errors Revamp (splitting PR #83106).

- Expensify Classic: Certinia articles (Auth, Export, Sync errors, FAQ). - Expensify Classic: add Sync-Errors hub page for Certinia so Sync-Errors articles are reachable (Auth and Export hubs already on main). Part of Integration Errors Revamp (splitting PR #83106).

…y Classic) - New Expensify: articles for Auth, Connection, Export, Sync errors, FAQ, plus root Configure/Connect/Troubleshooting. Removed placeholder files. - Expensify Classic: same structure and error articles. - Hub pages for both already exist on main. Part of Integration Errors Revamp (splitting PR #83106).

- Root: Configure, Connect, Troubleshooting. - Troubleshooting: Auth, Connection, Export, Sync errors, FAQ. - Hub pages already exist on main. Part of Integration Errors Revamp (splitting PR #83106).

- Root: Configure, Connect, Xero-Troubleshooting. - Troubleshooting: Auth, Connection, Export, Sync errors, FAQ. - Hub pages already exist on main. Part of Integration Errors Revamp (splitting PR #83106).

stephanieelliott assigned CortneyOfstad Feb 20, 2026

melvin-bot bot assigned stephanieelliott Feb 20, 2026

stephanieelliott changed the title ~~Integration Errors Revamp Testing~~ [HOLD] Integration Errors Revamp Testing Feb 20, 2026

github-actions bot changed the title ~~[HOLD] Integration Errors Revamp Testing~~ [No QA] [HOLD] Integration Errors Revamp Testing Feb 20, 2026

CortneyOfstad added 24 commits February 26, 2026 12:51

Update and rename NS0739 Sync Error to NS0739-Sync-Error.md

0b6ed84

Update and rename NS0942 Sync Error to NS0942-Sync-Error.md

5a59c4e

Rename NS0005 Export Error to NS0005-Export-Error.md

ef34b2c

Update NS0005-Export-Error.md

e098e61

Update and rename NS0012 Export Error to NS0012-Export-Error.md

65f126e

Update and rename NS0019 Export Error to NS0019-Export-Error.md

7440

4743c11

Update and rename NS0021 Export Error to NS0021-Export-Error.md

36a1f31

Update and rename NS0023 Export Error to NS0023-Export-Error.md

323a7d5

Update and rename NS0024 Export Error to NS0024-Export-Error.md

05aeb86

Update and rename NS0029 Export Error to NS0029-Export-Error.md

0beae62

Update and rename NS0033 Export Error to NS0033-Export-Error.md

5d449c1

Update and rename NS0034 Export Error to NS0034-Export-Error.md

3803c23

Update and rename NS0037 Export Error to NS0037-Export-Error.md

8e8a77f

Update and rename NS0042 Export Error to NS0042-Export-Error.md

570a4c6

Update and rename NS0045 Export Error to NS0045-Export-Error.md

40a6820

Update and rename NS0046 Export Error to NS0046-Export-Error.md

22feb70

Update and rename NS0055 Export Error to NS0055-Export-Error.md

0f7bd4c

Update and rename NS0056 Export Error to NS0056-Export-Error.md

09e0f41

Update and rename NS0059 Export Error to NS0059-Export-Error.md

f4c7b98

Update and rename NS0061 Export Error to NS0061-Export-Error.md

d02f20a

Update and rename NS0068 Export Error to NS0068-Export-Error.md

1619554

Update and rename NS0077 Export Error to NS0077-Export-Error.md

a2386b0

Update and rename NS0079 Export Error to NS0079-Export-Error.md

ac14633

Update and rename NS0085 Export Error to NS0085-Export-Error.md

9081998

stephanieelliott mentioned this pull request Mar 10, 2026

[No QA] Add Expensify Classic NetSuite troubleshooting docs #84812

Merged

stephanieelliott mentioned this pull request Mar 10, 2026

[No QA] Add Certinia troubleshooting docs (Expensify Classic only) #84814

Merged

54 tasks

stephanieelliott mentioned this pull request Mar 10, 2026

[No QA] Add QuickBooks Desktop troubleshooting docs (New + Classic) #84815

Merged

stephanieelliott mentioned this pull request Mar 10, 2026

[No QA] Add QuickBooks Online troubleshooting docs (New Expensify) #84816

Merged

stephanieelliott mentioned this pull request Mar 10, 2026

[No QA] Add QuickBooks Online troubleshooting docs (Expensify Classic) #84817

Merged

stephanieelliott mentioned this pull request Mar 10, 2026

[No QA] Add Sage Intacct troubleshooting docs (New Expensify) #84818

Merged

stephanieelliott mentioned this pull request Mar 10, 2026

Add Sage Intacct troubleshooting docs (Expensify Classic) #84820

Merged

stephanieelliott mentioned this pull request Mar 10, 2026

[No QA] Add Xero troubleshooting docs (New Expensify) #84821

Merged

stephanieelliott mentioned this pull request Mar 10, 2026

[No QA] Add Xero troubleshooting docs (Expensify Classic) #84822

Merged

stephanieelliott closed this Mar 12, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[No QA] [HOLD] Integration Errors Revamp Testing #83106

[No QA] [HOLD] Integration Errors Revamp Testing #83106
stephanieelliott wants to merge 1084 commits intomainfrom
helpsite-integration-error-revamp

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants