[!NOTE]
This is the second part in a multi-part series of PRs that will refactor existing Edge extension unit and functional tests to use the JSON comparison tool from AEPTestUtils
See part 1: #434 (Please merge part 1 first, as this branch incorporates its changes.)
Description
This PR refactors the rest of the Edge extension unit tests to use the test helper utilities from AEPTestUtils
Questions for reviewers
In RequestBuilderTests.swifttestGetPayloadWithExperienceEvents_withEventXdm_verifyEventId_verifyTimestamp
and
testGetPayloadWithExperienceEvents_withQuery_responseContainsQuery
Was it intended to not do a count check? There was no element count check post-flattening (pre-migration). To mirror this non-strict element check the JSON comparison currently does an extensible comparison instead of strict equality.
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Description
This PR refactors the rest of the Edge extension unit tests to use the test helper utilities from
AEPTestUtils
Questions for reviewers
In
RequestBuilderTests.swift
testGetPayloadWithExperienceEvents_withEventXdm_verifyEventId_verifyTimestamp
andtestGetPayloadWithExperienceEvents_withQuery_responseContainsQuery
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: