[TESTING] Add unit tests for stroopsToXlm and xlmToStroops unit conversion helpers

[chizzy192]

Metadata

Field	Value
Domain	Testing
Difficulty	Easy (1–2 Days)
Effort Estimate	effort: 2h
Priority	P2-Medium
Labels	good first issue, easy, Stellar Wave
Target Branch	dev
Depends On	None

🎯 Context & Goal

Converting between Stellar stroops (1 XLM = 10,000,000 stroops) and human-readable decimal XLM/USDC amounts must be accurate down to the single stroop. Floating point math can introduce precision errors when handling financial balances.

This issue creates unit tests in tests/unit/utils/unit-conversion.test.ts testing stroopsToXlm() and xlmToStroops() across boundary values (0, 1 stroop, fractional stroops, 100,000 XLM).

📂 Target Files

• tests/unit/utils/unit-conversion.test.ts -> Unit conversion test suite
• src/utils/unit-conversion.utils.ts -> Conversion utility functions

📋 Implementation Tasks

• Implement stroopsToXlm(stroops: bigint | string): string using Decimal.js
• Implement xlmToStroops(xlm: string | number): bigint using Decimal.js
• Write unit tests verifying boundary values and preventing floating-point precision loss

🛠️ Technical Guidance

import Decimal from 'decimal.js';

export function stroopsToXlm(stroops: bigint | string): string {
  return new Decimal(stroops.toString()).dividedBy(10000000).toFixed(7);
}
export function xlmToStroops(xlm: string | number): bigint {
  return BigInt(new Decimal(xlm).times(10000000).toFixed(0));
}

🔗 References & Related

• Stellar Precision Docs

⏳ Delivery Window

This issue should be completed within 1 day(s) of assignment.

Contribution Workflow

1. Branch off dev: git checkout -b feature/descriptive-name dev
2. Implement all tasks in the checklist above.
3. Run all CI checks locally (see DEVELOPMENT.md).
4. Open a Pull Request targeting dev.
5. Link this issue in your PR description: Closes #XX.

✅ Acceptance Criteria

• All implementation tasks above are completed.
• Code compiles/builds without errors.
• All existing tests continue to pass.
• New tests are added with >80% coverage of new code.
• Code follows project style guidelines (formatting, linting).
• PR targets dev branch (NOT main).
• PR description references this issue.
• Documentation is updated if public API changed.

[Muyideen-js]

@Muyideen-js has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi! I'm a full-stack developer with Stellar ecosystem experience. I've reviewed this issue and can deliver a quality fix. Please assign this to me!

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

[emynogithub]

@emynogithub has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I am an active and reliable contributor who consistently delivers quality work and adds value to the Drips Network community.

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

[baling-1]

@baling-1 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi team! I’d love to work on this issue. I have experience contributing to open source and enjoy delivering clean, well-tested solutions. ETA: 4 hours.

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

[Chidubemkingsley]

@Chidubemkingsley has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

can i work on this

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

[drips-wave]

Congratulations, @Chidubemkingsley! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Chidubemkingsley: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @Chidubemkingsley as part of the Stellar Wave Program's 7th Wave 🥳

😎 @Chidubemkingsley: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

[namdamdoi68-oss]

Hi maintainer, I noticed that my PR #187 was merged to resolve and close this issue, but the Drips Wave bot credited the points to @Chidubemkingsley because they held the assignment.

Could you please check if it's possible to update the Drips assignment for Issue #175 so the points are credited to PR #187 (namdamdoi68-oss)? Thank you for your time and help!