-
Notifications
You must be signed in to change notification settings - Fork 0
applications smoke harness
factory-droid[bot] edited this page Jul 5, 2026
·
1 revision
Active contributors: Douwe de Vries, vriesd
The smoke harness runs core QA Scribe workflows without the Tauri GUI. It gives CI and local development a fast way to catch storage, attachment, generation context, and cascade regressions.
| File | Purpose |
|---|---|
crates/qa-scribe-app/src/main.rs |
Main non-GUI smoke workflow. |
crates/qa-scribe-app/src/generation_smoke.rs |
Scripted provider workflow for generation smoke coverage. |
package.json |
Defines bun run smoke as cargo run -p qa-scribe-app. |
The harness uses qa-scribe-core directly. It creates core objects, writes them through SessionService, exercises attachment and draft behavior, reconciles state, and verifies deletion behavior. Because it bypasses the webview, failures usually point to Rust core or storage regressions rather than React view issues.
The smoke harness validates Rust core, Managed attachments, and AI-assisted Testware at the core workflow level.
- QA Scribe
- Download overview video (MP4)
- Architecture
- Getting started
- Glossary
- By the numbers
- Lore
- Fun facts
- Video overview
- How to contribute
- Development workflow
- Testing
- Debugging
- Patterns and conventions
- Tooling
- Applications
- Desktop app
- Smoke harness
- Systems
- Rust core
- Tauri command bridge
- Frontend shell
- Generation jobs
- Provider detection
- Release tooling
- Features
- Session capture
- Rich record editing
- Managed attachments
- AI-assisted Testware
- Settings and provider setup
- Crates
- qa-scribe-core
- qa-scribe-app
- Primitives
- Session
- Entry
- Finding
- Draft
- Evidence
- API
- Tauri commands
- Deployment
- Security
- Background
- Architecture decisions
- Migration context
- Cleanup opportunities
- TODOs and FIXMEs
- Complexity hotspots
- Reference
- Configuration
- Data models
- Dependencies