review_service unit tests misconfigure async mocks — 13 of 19 tests fail

[ascherj]

The service code correctly awaits db.execute(...), but the tests build their mock session so that result.scalars() returns a coroutine, causing AttributeError: 'coroutine' object has no attribute 'first' (and 'all') inside otherwise-correct service code. Rework the mock setup (e.g. AsyncMock for execute, MagicMock for the result object) so the existing CRUD tests actually run.

Steps to reproduce: pytest tests/unit/test_review_service.py -q — observed: 13 failed, 6 passed.

[jgarcdev]

Acquired

[MEMOMG8]

Claiming this for my Week 7 AI201 contribution. Planning to rework the mock setup in test_review_service.py (AsyncMock for execute, MagicMock for the result object) so the 13 failing CRUD tests pass. Will follow up with my solution plan soon.

[Aqureshi106]

I'd like to work on this one — planning to rework the mock setup in tests/unit/test_review_service.py (AsyncMock for db.execute, plain Mock/MagicMock for the returned Result object) so the 13 failing tests pass without changing core/services/review_service.py.

[Ariunlag]

I want work on this

[rdv-chio]

Claiming this bug

[rnossair]

I'd like to work on this issue. I plan to rework the mock setup in tests/unit/test_review_service.py so the 13 failing tests pass without modifying the review service code itself.

[mmicat]

working on this issue!

[alimakki1661]

Hi, I’d like to work on this issue.

[tbnguye9]

I'll be working on this for a course assignment (CodePath AI201).