fix: stabilize apps:diff 404 tests by mocking both apps#3585
Merged
Conversation
michaelmalave
temporarily deployed
to
AcceptanceTests
GitHub Actions
Inactive
michaelmalave
temporarily deployed
to
AcceptanceTests
GitHub Actions
Inactive
michaelmalave
temporarily deployed
to
AcceptanceTests
GitHub Actions
Inactive
michaelmalave
temporarily deployed
to
AcceptanceTests
GitHub Actions
Inactive
eablack
approved these changes
Mar 12, 2026
tlowrimore-heroku
pushed a commit
that referenced
this pull request
Mar 12, 2026
tlowrimore-heroku
added a commit
that referenced
this pull request
Mar 12, 2026
* updates CHANGELOG with new feature / refactor notes * fix: stabilize apps:diff 404 tests by mocking both apps (#3585) --------- Co-authored-by: Michael Malave <michael.malave@salesforce.com>
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
2 participants
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.
Summary
This fixes flakiness in two tests that only mocked app1 where app2 was unmocked and could fail first.
Type of Change
Breaking Changes (major semver update)
!after your change type to denote a change that breaks current behaviorFeature Additions (minor semver update)
Patch Updates (patch semver update)
Testing
Notes:
CI passes
Related Issues
GitHub issue: #[GitHub issue number]
GUS work item: W-17818328