Add Tests for Error Message Clarity and Mapping

[Jagadeeshftw]

Description:

Add tests (and small tooling) to ensure that important error codes from contracts map to clear, user-facing error messages in the backend and SDK, reducing ambiguity for integrators.

Requirements and context:

• Errors are surfaced in multiple layers (contract, backend, SDK)
• Need tests that:
  • Trigger representative errors on-chain
  • Verify backend/SDK mapping to human-readable messages
• Component locations:
  • Contract error enums and tests
  • Backend or SDK error mapping code

Suggested execution:

1. Fork the repo and create a branch

   git checkout -b test/error-message-clarity-mapping

2. Implement changes

   • Add mapping tables and tests for them
   • Ensure no important contract error is unmapped

3. Test and commit

   • Run backend/SDK tests
   • Include mapping table or reference in PR

Example commit message:

test: add tests for error message clarity and mapping

Guidelines:

• Assignment required before starting
• PR description must include: Closes #[issue_id]

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Naomi-Gift]

@Naomi-Gift has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Can i please be assigned to work on this ?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Naomi-Gift to this issue.