Add IPFS Upload Failure and Recovery Integration Tests

[Emmyt24]

title: Add IPFS Upload Failure and Recovery Integration Tests

Description:
Test metadata upload failures, timeouts, partial successes, and retries so the token deployment flow remains predictable under IPFS degradation.

Requirements and Context:

• Metadata is optional but operationally sensitive
• Users need clear paths when upload succeeds but contract submission fails, or vice versa
• Must cover upload services and deploy UI together

Suggested Execution:
Fork and Branch

• git checkout -b test/ipfs-failure-recovery

Implement Changes::
Files to Edit:

• frontend/src/services/IPFSService.ts - Make failure handling deterministic in tests
• frontend/src/hooks/useIPFSUpload.ts - Preserve actionable error state
• frontend/src/hooks/useTokenDeploy.ts - Handle mixed IPFS and contract failures cleanly

Files to Create:

• frontend/src/test/integration/ipfs-failure-recovery.integration.test.ts - IPFS failure flow tests

Test

• Verify upload timeout shows retryable error
• Verify invalid metadata payloads fail before upload
• Verify successful upload with failed contract submission preserves metadata URI for retry

Commit

• git add .
• git commit -m "test(integration): add ipfs failure and recovery coverage"

Guidelines:

• Distinguish upload failure from chain submission failure
• Keep retries explicit and observable

---

[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

[sparynx]

@sparynx has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I am a dedicated software developer with extensive experience building scalable web applications using Next.js and designing robust APIs to power seamless user experiences. My technical background includes a deep understanding of modern frontend architectures and backend integration, which I am eager to leverage to support the Drips mission of decentralized dependency funding. Having worked with the Drips SDK and Ethereum-based protocols, I am confident in my ability to contribute high-quality code that advances open-source sustainability. I am particularly interested in this issue because it aligns with my goal of building transparent, on-chain financial tools for the global developer community.

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

[drips-wave]

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

🧑‍💻 @sparynx: 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 🌊