Title: Verify "Payment operations" page.

Description:

This task is to write and execute automated test cases for various UI elements and functionalities on the "Payment Operations" page. The tests should validate that key UI elements are present and that core functionalities operate as expected.

Objective:

Ensure that the "Payment Operations" page displays all key elements and that interactions like searching, filtering, and report generation work as intended. The task will include multiple test cases covering these areas.

Pre-requisites:

Create a dummy connector
Use the SDK to process a payment

Test Cases:

Test Case 1: Verify Default Elements on "Payment Operations" Page

• Pre-requisites: User must be logged in.
• Steps:
  1. Navigate to the "Payment Operations" page using the side menu.
  2. Verify the search box is present with the placeholder "Search payment id."
  3. Verify the dropdown to select the time range is present.
  4. Verify the "Add Filters" button is present and visible.
  5. Verify the "Generate reports" button is present and visible.
  6. Verify the "Customize columns" button is present and visible.
• Expected Results:
  • Redirects to "Payment Operations" page.
  • Search box should be present with placeholder "Search payment id."
  • Dropdown should be visible.
  • "Add Filters" button should be present and visible.
  • "Generate reports" button should be present and visible.
  • "Customize columns" button should be present and visible.

Test Case 2: Verify Payments Displayed

• Pre-requisites: Make 3 payments.
• Steps:
  1. Login to the application.
  2. Navigate to the "Payment Operations" page.
• Expected Results:
  • 3 payments should be present in the table with valid payment details.
  • The table should contain the following columns:
    • S.No
    • Payment ID
    • Connector
    • Connector Transaction ID
    • Amount
    • Payment Status
    • Payment Method
    • Payment Method Type
    • Card Network
    • Customer Email
    • Merchant Order Reference Id
    • Description
    • Metadata
    • Created

Acceptance Criteria:

1. All test cases should pass with the expected results.
2. Each test case must verify the required functionality or UI element.
3. The tests should be included in the regression suite and executed in the CI/CD pipeline.

Submission Process:

• Ask the maintainers for assignment of the issue, you can request for assignment by commenting on the issue itself.
• Once assigned, submit a pull request (PR).
• Maintainers will review and provide feedback, if any.
• Maintainers can unassign issues due to inactivity, read more here.
• For this issue, please submit a PR on juspay/hyperswitch-control-center repo, and link it to the issue.

Refer here for Terms and conditions for the contest.