Fix TestBase timeout#1099
Merged
timkimadobe merged 2 commits intoadobe:dev-testutilsfrom Oct 28, 2024
Merged
Conversation
…alue in both cases Update documentation text for methods in TestBase
praveek
approved these changes
Oct 28, 2024
addb
approved these changes
Oct 28, 2024
10 tasks
This was referenced Oct 28, 2024
Merged
10 tasks
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.
Important
This change will bump AEPTestUtils from 5.2.1 -> 5.2.2
Description
This PR fixes TestBase method
getDispatchedEventsWith(type:source:timeout:file:line:)to respect the provided timeout value in both cases (when event expectation does or doesnt exist for a given event type and source).It also updates the method documentation for some methods.
Related Issue
This Edge iOS integration test failed because the default timeout did not allow enough time for event processing before moving on to assertion. Without the change in this PR, there is also no way to configure the non-expected event timeout period.
Notice in the following logs, that the expected Edge error response IS dispatched, but there the timeout triggers too quickly and the assertion fails:
Logs archive
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: