-
Notifications
You must be signed in to change notification settings - Fork 0
primitives entry
factory-droid[bot] edited this page Jul 5, 2026
·
1 revision
Active contributors: Douwe de Vries, vriesd
An Entry is raw testing material captured during a Session. Current UI centers on note-style Entries, and the domain also represents observations, API responses, logs, and possible findings.
| File | Purpose |
|---|---|
crates/qa-scribe-core/src/domain/entry.rs |
Entry DTOs, drafts, patches, and entry type values. |
crates/qa-scribe-core/src/services/session_service/entries.rs |
Entry persistence and validation. |
src-tauri/src/commands/entries.rs |
Entry bridge commands. |
frontend/src/views/SessionEditorView.tsx |
Note Entry editing. |
Entries feed AI-assisted Testware through Generation Contexts and can become Evidence for Findings.
- 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