[CYPRESS]: Verify misc features in "Payment operations" page.

---

Title: Verify misc features in "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: Generate Payment Reports

• Pre-requisites: Make a payment.
• Steps:
  1. Login to the application.
  2. Navigate to the "Payment Operations" page.
  3. Click on "Generate Reports."
  4. Select a time range and click "Generate."
• Expected Results:
  • A "Generate Payment Reports" popup should appear.
  • An "Email sent" popup should appear.
  • Check mail inbox for a CSV file with payment details.

Test Case 2: Verify "Copy to Clipboard" Button for Payment ID

• Pre-requisites: Make a payment.
• Steps:
  1. Login to the application.
  2. Navigate to the "Payment Operations" page.
  3. Click on the "Copy" button beside a payment ID.
  4. Paste the copied ID in the payment search box and hit "Enter."
• Expected Results:
  • Payment ID should be copied to the clipboard.
  • The ID should appear in the search box, and the resulting entry should contain the same payment ID.

Test Case 3: Verify "Open in New Tab" Button for Payment ID

• Pre-requisites: Make a payment.
• Steps:
  1. Login to the application.
  2. Navigate to the "Payment Operations" page.
  3. Click on the "Open in new tab" button beside a payment ID.
• Expected Results:
  • The payment page should open in a new tab.

---

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.

---