add e2e smoke test for edm4u upm package #884
Open
+189
−73
Conversation
This file contains 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
twometresteve
approved these changes
Feb 21, 2025
Co-authored-by: Steve Kirkland <[email protected]>
Build size impact
Generated by 🚫 Danger |
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.
Goal
there are no working e2e tests to make sure that our EDM4U package is working as expected.
Changes
Testing
Added a smoke test to make sure that the correct android libs are dynamically pulled in and that an error can be sent.
If something goes wrong then the SDK would not be able to init and no errors would be sent.
This is just a smoke test as not notifier code is changed and we only really need to know that the SDK can init.