Docs

For Developers

StratoSort Stack Testing Guide

Applies to: StratoSort Stack 5.0.x
Purpose: Single source of truth for manual QA and automated test expectations.


1) Quick Manual Checklist (Smoke Test)

Use this checklist before release candidates and before merging changes that impact user workflows. Every item should pass. If time is limited, focus on Sections A-C.

A. Launch and Baseline

B. File Intake and Analysis

C. Organization and Safety

D. Search and Knowledge Graph

E. Resilience


2) Detailed Feature QA

Work through these sections when testing specific features or validating a branch with broad changes.

F. Model Setup Wizard

G. Welcome Phase

H. Smart Folder Setup (AddSmartFolderModal)

I. Discover Phase and Naming Settings

J. Organize Modals

Triage Modal

Duplicate Resolution Modal

Tag Cluster Modal

K. Unified Search Modal (Full)

L. Chat Panel

M. Settings Panel (All Sections)

Open Settings (gear icon or nav bar) and walk through each collapsible section.

AI Configuration

Performance

Default Locations

Application

Settings Persistence

N. Navigation Bar

O. UI Components (Visual Spot-Check)


3) Automated Test Commands

Run these locally before opening a PR.

# Formatting and lint
npm run format:check
npm run lint

# Unit/integration tests
npm test

# Optional deeper coverage
npm run test:integration
npm run test:coverage

# Optional E2E (slower)
npm run build
npm run test:e2e

# Release-depth suites (optional, slow)
npm run test:stress   # Jest stress config
npm run test:soak     # long-running Playwright soak (SOAK=1, ~12 min)
npm run test:all      # npm test + test:stress

Notes:


4) Critical Test Focus Areas

Prioritize these paths when time is limited:

  1. Analysis pipeline: import -> validate -> extract -> classify -> render results.
  2. Organization safety: suggest -> apply move -> undo/rollback.
  3. Search quality: semantic search relevance and ranking stability.
  4. Chat accuracy: persona behavior, citation rendering, Fast vs Deep mode.
  5. Settings round-trip: change -> persist -> restart -> verify.
  6. IPC resilience: renderer/main interactions under repeated rapid actions.

5) Debugging and Troubleshooting

Log Locations

Common Issues

Symptom Probable Cause Recommended Fix
Analysis never starts Models unavailable Run npm run setup:models:check
OCR results are poor Tesseract OCR data missing Verify the bundled Tesseract WASM/data; OCR runs locally via Tesseract.js
Test flakiness Stale build artifacts Run npm run clean then re-run tests
Build/test environment Dependency drift Run npm ci to restore lockfile-based install
Settings don't persist localStorage quota full Clear app data or check console for quota errors
Graph view blank No embeddings built Run embedding rebuild from Settings
Chat returns empty Model not loaded or crashed Check AI health badge in Settings > AI Config

6) Reporting Bugs

When filing a bug report, include:

  1. Reproduction steps (exact sequence).
  2. Expected behavior and actual behavior.
  3. Environment (OS version, app version, hardware details when relevant).
  4. Relevant logs from the paths above.
  5. Screenshots or short screen recordings when the issue is visual.

Edit this page on GitHub