Automated Test Inventory Generation via Static Code Analysis
SpecVital is a platform that automatically generates test inventories from GitHub repositories using AST-based static analysis. Simply enter a repository URL and instantly see the complete test landscapeโno CI/CD integration required.
| Feature | Description |
|---|---|
| Instant | Results in seconds, not hours of setup |
| Accurate | Tree-sitter AST parsing, deterministic (not AI) |
| Multi-Language | Support for major test frameworks across languages |
GitHub URL โ AST Parsing (Tree-sitter) โ Test Inventory
- Enter a public GitHub repository URL
- SpecVital clones and parses test files using specvital/core
- View test suites, cases, and structure in a visual dashboard
Note: This is static analysisโwe parse test definitions, not execution results. You'll see what tests exist and their structure, not pass/fail status.
20+ test frameworks across multiple languages:
| Language | Frameworks |
|---|---|
| JavaScript/TypeScript | Jest, Vitest, Playwright, Cypress, Mocha |
| Go | testing |
| Python | pytest, unittest |
| Java | JUnit 5, TestNG |
| Kotlin | Kotest |
| C# | NUnit, xUnit, MSTest |
| Ruby | RSpec, Minitest |
| PHP | PHPUnit |
| Rust | cargo test |
| C++ | Google Test |
| Swift | XCTest |
See specvital/core for details.
SpecVital is in active development. Currently available:
- โ GitHub OAuth authentication
- โ Repository analysis via URL input
- โ Test tree visualization with statistics
- โ Multi-framework detection
- โ Filter and search capabilities
- โ Internationalization (English, Korean)
This repository contains the web application (Frontend + Backend API). The full system consists of:
| Repository | Role |
|---|---|
| specvital/web | Web dashboard + REST API |
| specvital/core | Parser library (Tree-sitter based) |
| specvital/collector | Background worker for analysis jobs |
| specvital/infra | Database schema and infrastructure |
- Engineering Managers: Understand team's test coverage landscape
- QA Leads: Manage automated test inventory across projects
- Staff Engineers: Map existing tests before legacy refactoring
- Questions & Ideas: GitHub Discussions
- Bug Reports: GitHub Issues
MIT
