Fix 3 ERM regressions introduced by Spend Request / IC inbox changes - #9883
Closed
v-rohangarg20 with Copilot wants to merge 1 commit into
Closed
Fix 3 ERM regressions introduced by Spend Request / IC inbox changes#9883v-rohangarg20 with Copilot wants to merge 1 commit into
v-rohangarg20 with Copilot wants to merge 1 commit into
Conversation
Copilot
AI
changed the title
[WIP] Fix test failures in Spend Request automation tests
Fix 3 ERM regressions introduced by Spend Request / IC inbox changes
Aug 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR #9391 introduced 3 ERM failures in
LegacyTestsBucket1: 1 new Spend Request regression and 2 NL intercompany tests that now stop on theComplete IC Inbox Actionrequest page. This change aligns the affected tests with the new Spend Request and IC inbox behavior without weakening coverage.Spend Request regression
CannotModifyReleasedSpendRequestto assert on an actual guarded mutation instead of a no-opModify(true).Purpose) so it exercisesTestStatusOpen()on released requests.NL intercompany request-page handling
RequestPageHandlerto:AutoAcceptICGenJnlTransactionUTOpenICPurchaseInvoiceWithVendorOrderNoExceeding20CharsComplete IC Inbox Actionafter the PR introduced request-page-driven behavior on those paths.Why this is the minimal fix