Mock Whisper transcription in endpoint tests

Open
#46 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
fastapi, python
Domain
api, backend, testing

Research direction

Start by locating the audio endpoint tests and reviewing how they invoke the Whisper model and local audio tooling. Run the endpoint test suite, replace transcription dependencies with mocks while preserving HTTP/WebSocket assertions, and document how to run any remaining real transcription test separately.

Written by the indexing model from the issue text.

Description

good first issue

Problem

Audio endpoint tests currently depend on the Whisper model and local audio tooling.

Acceptance criteria

  • Mock transcription for endpoint validation tests.
  • Keep assertions focused on HTTP/WebSocket behavior.
  • Document how to run any remaining real transcription test separately.
Dominant language
Python
Stars
3
Forks
10
Avg merge
14h 44m
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ashrafee-dev/scamshield-api

All issues in ashrafee-dev/scamshield-api

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.