[BE-146] vendors and purchase-orders modules have only single happy-path smoke tests

[yusuftomilola]

Overview

The only tests touching VendorsService/PurchaseOrdersService are two it() blocks in backend/src/ibinola.spec.ts ("VendorsService creates vendor records", "PurchaseOrdersService receives POs") — no co-located specs, no coverage of VendorsService.update(), and no coverage of the PO status-transition gaps called out in [BE-119]/[BE-120].

Tasks

• Move and expand coverage into backend/src/vendors/vendors.service.spec.ts and backend/src/purchase-orders/purchase-orders.service.spec.ts.
• Add coverage for VendorsService.update().
• Once [BE-119]/[BE-120] land, add tests for the full PO status state machine.

Acceptance Criteria

• Both modules have real, co-located coverage beyond their single existing happy-path tests.

Dependencies

PO transition coverage depends on [BE-119].

Notes for Contributors

Comment below to be assigned.

[DataRuth]

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

Hello,

I am highly interested in tackling this issue. I have carefully reviewed the requirements and mapped out an efficient path forward for the implementation. Please assign the issue to me if it is still available, and I will get started immediately.

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

[Gracora]

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

I will create dedicated co-located spec files for both Vendors and Purchase Orders modules, expanding beyond the current single happy-path tests to cover VendorsService.update and the full PO status-transition state machine. My plan is to mock repositories and test each service method with both success and error paths.

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

[drips-wave]

Congratulations, @Gracora! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@Gracora's PR #1373 was approved and merged by @yusuftomilola.

🏆 @Gracora: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (872 total points). Track your full progress on GrantFox.

👏 Great work, @Gracora! Keep contributing to DistinctCodes.

[drips-wave]

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

😎 @Gracora: 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.