In-App Message Unit Test Migration #2103
Open
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.
Description
One Line Summary
In-App Message Unit Test Migration
Details
Since its release, the Android User Model SDK has largely included only new tests and is lacking may important Player Model unit tests. Due to the significant updates to User Model, the existing unit tests on Player Model require significant refactoring.
Motivation
Provide a more comprehensive test suite to Android SDK.
Scope
This PR encompasses In-App Message unit tests only.
OPTIONAL - Other
Where possible, I've kept the original test names of the junit tests from Player Model for easier tracking.
Some considerations I'm still working through:
Testing
Unit testing
All tests in InApp MessagesTests.kt pass. Commented tests with "TODO" markers still need to be migrated/implemented.
Affected code checklist
Checklist
Overview
Testing
Final pass
This change is