android-branch-deep-linking-attribution
android-branch-deep-linking-attribution copied to clipboard
SDK 2228 DMA automation tests
Reference
SDK-2228 -- [Automation] DMA Compliance testing automation. https://branch.atlassian.net/browse/SDK-2228
Description
-> Updated Automation Test bed app for testing API setDMAParamsForEEA. -> In Home Screen Added two buttons - One for setting DMA Params and Another for logging event. Both button after calling corresponding Branch APIs open LoggingView Window, which prints logs for the operations performed. They show APIs posted with reuqest and response params. -> Added Scroll Bar in Home Screen.
Testing Instructions
- Run Appium Automation Tests using branch https://github.com/BranchMetrics/qentelli-saas-sdk-testing-automation/tree/SDK-2288-DMA-Compliance-Automation. Ref branch is added in workflow (for testing purpose).
- Compile, Run and Test App manually
NOTE "Set DMA Params" requires input parameters which either can be passed as program arguments or they can be set manually in source code before running program for testing purpose.
Example:
getIntent().putExtra("testData", "{\"dma_eea\":\"Yes\",\"dma_ad_personalization\":\"Yes\",\"dma_ad_user_data\":\"Yes\",\"Include\":\"Yes\",\"URL\":\"https:\\/\\/timber.test-app.link\\/80OHAnv8DHb\"}");
OR
--es "testData", {\"dma_eea\":\"Yes\",\"dma_ad_personalization\":\"Yes\",\"dma_ad_user_data\":\"Yes\",\"Include\":\"Yes\",\"URL\":\"https:\\/\\/timber.test-app.link\\/80OHAnv8DHb\"}"
When this App is lanuched through Appium Automations tests, Appium will pass these paramters as optionalIntentArguments
--> ref: SDK-2288-DMA-Compliance-Automation is added in Automation workflow just for testing. It will be removed later on.
Risk Assessment [HIGH
|| MEDIUM
|| LOW
]
LOW
- [X ] I, the PR creator, have tested — integration, unit, or otherwise — this code.
Reviewer Checklist (To be checked off by the reviewer only)
- [ ] JIRA Ticket is referenced in PR title.
- Correctness & Style
- [ ] Conforms to AOSP Style Guides
- [ ] Mission critical pieces are documented in code and out of code as needed.
- [ ] Unit Tests reviewed and test issue sufficiently.
- [ ] Functionality was reviewed in QA independently by another engineer on the team.
cc @BranchMetrics/saas-sdk-devs for visibility.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 38.04%. Comparing base (
1b6bb47
) to head (69cd050
).
Additional details and impacted files
@@ Coverage Diff @@
## master #1176 +/- ##
============================================
- Coverage 38.11% 38.04% -0.07%
+ Complexity 689 686 -3
============================================
Files 59 59
Lines 6279 6279
Branches 939 939
============================================
- Hits 2393 2389 -4
- Misses 3443 3444 +1
- Partials 443 446 +3
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.