Issue 522: Moved dateOfBirth field for IndividualSender to String type #531
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.



This pull request updates the handling of the
dateOfBirthfield in theIndividualSenderclass and significantly enhances the test coverage for payment session requests. The most important changes include switching the data type ofdateOfBirthto a string for better date formatting flexibility and adding comprehensive tests for payment sessions involving an individual sender. Additionally, utility methods have been introduced to streamline test data creation and response verification.Model changes:
dateOfBirthfield inIndividualSenderfromInstanttoStringto allow for direct input of formatted date strings [1] [2].Test improvements:
shouldRequestPaymentSessionsWithFullIndividualSender, which builds a completePaymentSessionRequestusing anIndividualSenderand verifies the API call and response.createStandardAddress,createSenderAddress,createStandardPhone,createStandardBilling,createDrivingLicenceIdentification, andcreateIndividualSenderto simplify and standardize test data creation.verifySuccessfulResponsefor consistency and readability.