[BE-142] categories module test coverage is a single happy-path smoke test

[yusuftomilola]

Overview

Like locations, the only test touching CategoriesService is one it() in the misplaced backend/src/femaleotaku.spec.ts ("CategoriesService manages depreciation defaults"), with no co-located spec file and no coverage of not-found paths, update, or delete.

Tasks

• Move and expand coverage into backend/src/categories/categories.service.spec.ts.
• Cover the depreciation-defaults logic more thoroughly (its edge cases aren't visible from the single existing assertion), plus not-found and update/delete paths.

Acceptance Criteria

• Categories has real, co-located test coverage beyond the single existing test.

Notes for Contributors

Comment below to be assigned.

[Paranoa-dev]

I’d like to take this on. I’ll move the existing CategoriesService coverage into a dedicated backend/src/categories/categories.service.spec.ts and expand it into proper co-located unit coverage.

I’ll cover the depreciation-defaults behavior and relevant edge cases, along with not-found handling and the update/delete paths. I’ll follow the existing service testing patterns and keep the changes limited to the category service tests, removing or relocating the misplaced coverage from femaleotaku.spec.ts as appropriate.

I’ll run the focused categories service test suite and the relevant lint/type checks, then verify the existing backend tests remain green before submitting the PR.

[Magrexy]

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

I will improve test coverage for the Categories module by creating a co-located spec file and expanding tests to cover depreciation defaults, not-found paths, and update/delete operations. My approach is to move existing tests into a dedicated service spec and systematically add edge-case assertions.

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

[drips-wave]

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

🧑‍💻 @Magrexy: 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!

@Magrexy's PR #1372 was approved and merged by @yusuftomilola.

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

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

[drips-wave]

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

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