Repowise · Codebase intelligence
mvrahden / go-test
Go test suite framework powered by code generation — BDD vocabulary, lifecycle hooks, fixtures, snapshots. Zero reflection, zero runtime deps.
Languages
- go82.7%
- typescript10.7%
- markdown3.9%
- yaml1.5%
- json0.6%
- makefile0.3%
- javascript0.3%
Explore mvrahden/go-test
Files, symbols, languages, packages, git intelligence
Interactive view of how files import each other
Files with the most churn and co-change risk
Bus-factor and per-file maintainer maps
Architectural decisions extracted from commits and PRs
Unreachable symbols and unused exports
Module-by-module documentation generated from source
Ask grounded questions over the indexed code
Key modules2
- go
examples
examples
- typescript
vscode-gotest
vscode-gotest
Entry points8
cmd/gotest-lint/main.goexamples/search/index.gointernal/gotestgen/testdata_e2e/fixture_lifecycle/main.gointernal/gotestgen/testdata_e2e/multi_fixture/main.gointernal/gotestgen/testdata_e2e/no_testfiles/main.gointernal/gotestgen/testdata_e2e/no_testsuite/main.gointernal/gotestgen/testdata_e2e/suite_guard/main.gointernal/gotestgen/testdata_e2e/testsuite/main.go
How mvrahden/go-test works
Go test suite framework powered by code generation — BDD vocabulary, lifecycle hooks, fixtures, snapshots. Zero reflection, zero runtime deps. This page is an auto-generated, always-fresh map of the mvrahden/go-test repository, written primarily in Go. Repowise indexes the source, parses every symbol, computes a dependency graph, mines git history for hotspots and ownership, and lifts the resulting architectural decisions into a wiki you can read or query through MCP.
The codebase has 335 source files, 2,147 symbols, and 7 languages, structured as a monorepo with 2 packages. Git churn analysis flags 82 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 90 tightly-coupled module communities.
Use the panels above to open the interactive dashboards, or connect this repo to your editor via the Repowise MCP server for grounded answers inside Claude, Cursor, or VS Code.