PaymentsApp API unit tests

[gcatanese]

Add unit testing for PaymentsApp API

[gemini-code-assist]

Summary of Changes

Hello @gcatanese, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on significantly improving the test coverage for the PaymentsApp API by introducing a new set of unit tests. It also includes necessary enhancements to the existing testing framework and adds mock data to facilitate robust and isolated testing of API interactions.

Highlights

• New Unit Tests for PaymentsApp API: I've added a comprehensive suite of unit tests for the PaymentsApp API in a new test class, PaymentsAppTest.java. These tests cover various operations, including generating boarding tokens for merchants and stores, listing payments apps with and without parameters, and revoking payments apps, ensuring the API's functionality is thoroughly validated.
• Enhanced Test Infrastructure: I've updated the BaseTest.java utility class to improve its HTTP client mocking capabilities. This includes adding support for mocking requests that contain non-null request bodies and making argument matching more flexible, which is crucial for accurately simulating API interactions in tests.
• New Mock Data Files: To support the new unit tests, I've introduced several new JSON files under src/test/resources/mocks/paymentsapp/. These files provide realistic mock responses for both successful and error scenarios across different PaymentsApp API endpoints.
• Deprecation Message Clarification: A minor change was made to PosTerminalManagementApi.java to update and clarify a deprecation message, directing users to the appropriate Management API instead of specific payment services.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces unit tests for the PaymentsApp API, covering success and error scenarios. The changes to BaseTest.java enhance mocking capabilities. The review focuses on improving test readability and robustness.