brief

Testing

Current State

This repo currently has:

• no _test.go files
• no test runner scripts in the repo
• no committed testdata/ directory

The current verification workflow is a mix of:

• go build ./...
• go vet ./...
• manual CLI testing
• dogfooding recorded in brief

Manual Dogfood Coverage

A full manual pass was executed across these areas:

• smoke post/get round-trip
• category behavior
• tag operations
• put/update operations
• FTS behavior
• deprecate / undeprecate lifecycle
• hard delete lifecycle
• edge cases and input validation
• JSON output
• config and --db

Real Bugs Found During Dogfooding

These bugs were found and fixed during the manual pass:

• deprecated entries were visible via brief get --id <id> without --include-deprecated
• explicit brief get --limit 0 fell back to the default limit instead of rejecting the value
• successful command output, including JSON, was emitted to stderr instead of stdout

Earlier dogfood bugs also fixed in this repo:

• post --stdin ignored piped input
• put --stdin silently no-op’d
• FTS combined with --tag produced an SQL error
• FTS prefix search on partial words did not return expected matches

What To Run

Repository-level checks:

go build ./...
go vet ./...

Installed CLI smoke checks:

brief --help
brief get --recent
brief category list
brief tag list

Notes

The dogfood/admin work in this repo showed that concurrent write commands against the same SQLite DB can hit SQLITE_BUSY. Serial writes are safer for operational scripts and manual maintenance.