[Phase 5] Tests unitaires pour fractal-stt #322
Labels
No labels
module:M0-setup
module:M1-stt
module:M1-stt
module:M2-ai
module:M2-ai
module:M3-rich
module:M3-rich
module:M4-bridge
module:M4-bridge
module:M5-bonus
module:M5-bonus
module:setup
priority:high
priority:high
priority:low
priority:low
priority:medium
priority:medium
type:chore
type:chore
type:feature
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/my-fractal#322
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Contexte
La crate
fractal-stt(M1 — Speech-to-Text) est la seule crate métier sans issue de tests unitaires dédiée. Les autres crates ont toutes leur issue : fractal-ai (#316), fractal-rich (#317), fractal-bridge (#318), fractal-core (#319), fractal-gtk (#320).Critères d'acceptation
SttEngineet ses types communs (AudioData,Transcript,TranscriptSegment)WhisperEngine(sans subprocess réel)ModelManager: logique de sélection et vérification de chemin localevent_id→Transcript)ConfidenceSttEnginepour les tests d'intégration (pipeline sans moteur réel)Notes techniques
whisper-cppni les API cloud dans les tests unitaires — tout doit être mockable via le traitSttEnginecrates/fractal-stt/src/(trait, moteurs, pipeline, cache)