[TESTING & QA] Test edge case: empty arrays in listing and project responses

[dev-fatima-24]

Priority: medium

Description

Components that render lists (marketplace listings, project credit batches, provenance events) must be tested with empty arrays to ensure they render the correct empty state rather than crashing. This is a common source of production bugs.

Acceptance Criteria

• Marketplace renders empty state when listings array is []
• Project detail renders empty state when credit_batches array is []
• ProvenanceTrail renders empty state when events array is []
• BulkPurchaseCart renders empty state when items array is []
• All empty states match the designed empty state components

[aliyuHabibu]

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

I can pick this up.

Empty array crashes are annoying and easy to miss if you only test with seeded data. I’ll go through each component and make sure they handle [] gracefully.

Plan:

1. Write/update tests for Marketplace, ProjectDetail, ProvenanceTrail, and BulkPurchaseCart to pass empty arrays and assert the empty state renders.
2. Check the render logic, most crashes come from calling .map() or accessing length on undefined, or assuming the first item exists. I’ll add guards and fallback UI where needed.
3. Match design: I’ll pull the empty state components from Figma/components and make sure the tests assert against those exact components, not just generic “no data” text.
4. No behavior changes for non-empty states. This is test + small defensive fixes only.

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

[Timothy2025-20]

@Timothy2025-20 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi team, am a software engineer with her of experience and I would love to address and resolve this issue if assigned to me. Thank you 🙏

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

[drips-wave]

Congratulations, @Timothy2025-20! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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