Skip to content

Glossary ​

🇰🇷 한국어 버전

Domain terminology used across the Specvital platform.

Core Domain ​

TermDefinition
CodebaseA GitHub repository registered for analysis (host + owner + name)
AnalysisA single parsing job for a codebase at a specific commit
InventoryComplete collection of test files parsed from a codebase
Test SuiteA group of related tests (e.g., describe block in Jest)
Test CaseAn individual test (e.g., it/test block)
FrameworkTest library used (Jest, Vitest, Playwright, Go testing, pytest, etc.)

Test Status ​

TermDefinition
activeNormal test that will run
skippedTest marked to be skipped (.skip, t.Skip())
todoPlaceholder test not yet implemented (.todo)
focusedTest marked to run exclusively (.only)
xfailExpected failure test (@pytest.mark.xfail)

Analysis Status ​

TermDefinition
pendingAnalysis queued but not started
runningAnalysis in progress
completedAnalysis finished successfully
failedAnalysis encountered an error

Architecture ​

TermDefinition
CoreTest parser library (Go) - parses source code into test inventory
WorkerWorker repository - contains analyzer, scheduler, spec-generator binaries
WebFrontend (Next.js) + Backend API (Go Chi)
InfraDatabase schema and local development infrastructure
AnalyzerRiver-based process that consumes analysis tasks from PostgreSQL queue
SchedulerCron-based process that enqueues periodic refresh tasks

Technical Terms ​

TermDefinition
Tree-sitterIncremental parsing library used for AST-based code analysis
ASTAbstract Syntax Tree - structured representation of source code
RiverGo library for distributed task queue using PostgreSQL
sqlcGenerates type-safe Go code from SQL queries
AtlasDatabase schema migration tool

Source Types ​

TermDefinition
LocalSourceParser reads from local filesystem
GitSourceParser clones from remote Git repository

Open-source test coverage insights