SuresoftTechnologies/dvera-plugin

> 한국어: README.ko.md
DVERA (Dynamic Verification Agent) brings CT C/C++ verification work into coding agents such as Claude Code, Codex CLI, Cursor, and GitHub Copilot. It uses the working context of source code, requirements, build information, source changes, and existing test assets to prepare and request CT verification work.
CT (Controller Tester) is a test automation solution for unit, integration, and code-based testing of mission-critical C/C++ software. It brings together test-environment setup, test design and generation, execution, code-coverage analysis, reporting, and traceability management.
DVERA does not replace CT's verification results. The coding agent helps prepare and coordinate verification work; CT performs the analysis, build, test execution, and result aggregation. Generated tests must be reviewed for test intent, data, and expected results, then confirmed with actual execution results and measured coverage.
What the CT and DVERA workflow adds
| Verification need | CT and DVERA workflow |
|---|---|
| Complex C/C++ environments | Capture compiler, macro, include-path, toolchain, build, and target conditions before analysis. |
| Unit and integration verification | Design and execute tests at function, module, and interface levels, including existing GoogleTest assets where applicable. |
| Reviewable evidence | Connect test intent, execution results, statement/branch/MC/DC coverage, reports, and requirement links for review. |
| Repeated change verification | Re-run affected tests after code changes and review new failures and coverage deltas for regression follow-up. |
| AI-assisted test work | Use code, requirements, and change context to prepare test work, then improve it with CT analysis and measured results. |
Workflow at a glance
1. Prepare the compiler, macro, include-path, toolchain, and target context for a CT project.
2. Analyze the project and resolve environment or configuration issues through a controlled feedback loop.
3. Generate, execute, and improve unit or integration tests using build, execution, and coverage feedback.
4. Review coverage and results, produce reports, and re-run affected verification after source changes.
The Skills in this repository document that product-connected workflow. They are not standalone replacements for a CT installation.
Install
In Claude Code:
Or from a terminal:
Skills then load as /dvera:ct-init-project, /dvera:ct-test-loop, and so on. The plugin adds about 620 tokens to every session; each Skill body is read only when that Skill runs.
Product-backed actions need a deployed CT environment. Without one, a Skill stops at its installation check and shows how to reach product support.
Example requests
Trigger examples from the CT user guide. Responses can vary with the AI model and conversation context; if the result differs from what you expect, rephrase the request with more detail and retry.
| Request | Skill |
|---|---|
| Create a CT project and start verification. | ct-init-project |
| Run tests in CT. | ct-init-project |
| Generate tests for the calculate_checksum function. | ct-test-loop |
| Find functions without tests and generate tests for them. | ct-test-loop |
| Run regression tests. | ct-regression |
| Open CT. | ct-open |
Skills
All Skills require a deployed CT environment for their product-backed actions and stop with an installation notice when none is found.
| Skill | CT workflow stage |
|---|---|
| ct-init-project | Start or prepare a CT verification project. |
| ct-extract-macro | Capture target compiler macros and build-environment facts. |