docs: LNK-QA-UPDATE - Update QA playbook and Contribution guide

[gitstart-app]

This PR was created by GitStart to address the requirements from this ticket: LNK-QA-UPDATE.

---

Update QA playbook and Contribution Guide

This PR updates the documentation in CONTRIBUTING.md and QA_PLAYBOOK.MD to with more things to consider during implementation and more QA test cases.

Changes to contribution guide

• Added guidance on handling internal transfers that appear as two transactions on the PSP side.
• Clarified that creditor and debtor transactions should have unique payment_id values.
• Added new directive to update parent payment amounts when processing returns or refunds.
• Provided guidance on linking declined transactions to their pending transaction counterparts.
• Included recommendation for generating unique idempotency keys across deployments by incorporating connectorID.
• Polling behaviour and use of Periodically.

Changes to QA_PLAYBOOK.MD

Enhanced Polling Testcases

• Added verification steps for payment status updates and proper linking of adjustments.
• Added check for transaction ordering (oldest to newest).
• Added verification for proper handling of payment references and uniqueness.

Enhanced Transfers and Payouts Testing

• Added checks for internal transfers to ensure they create separate payments with one adjustment each.
• Added verification that creditor and debtor transactions don't share payment IDs.
• Added checks for proper handling of returns/refunds and updating parent payment amounts.
• Added verification for linking declined transactions to pending transactions.
• Added guidelines on handling Returns/Refunds

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.65%. Comparing base (933bad9) to head (aa3497b).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #435      +/-   ##
==========================================
- Coverage   69.66%   69.65%   -0.01%     
==========================================
  Files         627      627              
  Lines       32196    32196              
==========================================
- Hits        22428    22425       -3     
- Misses       8554     8556       +2     
- Partials     1214     1215       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.