iOS Integration Validator 2.0 #1439
Open
+372
−11
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.
Reference
No related JIRA ticket, part of the initiative to improve the Branch SDK implementation QA process.
Summary
Enhanced the iOS Integration Validator with multiple quality of life changes to improve developer experience, aid our support team to debug faster and improve the overall integration testing process.
Motivation
The current iOS integration validator is a good first step for any developer to test their Branch iOS SDK integration. However, it is missing a few key details that can make it easy for the developer to validate their integration. Additionally, there are three key pain points that are solved as quality of life enhancements:
Type Of Change
Testing Instructions
There are a total of 8 new changes that can be observed through this PR.
validate_integration=true
as a query parameter to any Branch link and click on it to trigger the Integration Validator. This complements the old method beautifully to give developers two great ways to trigger the validator.https://github.com/user-attachments/assets/a14334cd-7764-42a8-bbf0-b4e7b12773ca
cc @BranchMetrics/saas-sdk-devs for visibility.