Developer Tools¶
3forge Enterprise ships tooling that brings your editor and your test workflow directly onto a live deployment: language intelligence, step-debugging, and an isolated unit-test runner, backed by Enterprise's own parser and runtime.
Overview¶
-
VS Code Extension
AmiScript/AMISQL language support and live debugging inside VS Code, connected to a running AmiCore instance.
-
Language and Debug Servers
The LSP and DAP servers embedded in AmiCore that power the editor experience. Enable and configure them here.
-
Unit Testing
Run AmiScript unit tests against a Center in an isolated, throwaway clone, with line and branch coverage.
-
Center Debugger
Stop-the-world step-debugging of server-side AmiScript from a plain command surface: breakpoints, stepping, and inspection, with no IDE required.
-
Code Coverage
Line and branch coverage of server-side AmiScript, from a test run or a live Center, with cobertura/lcov/HTML output for CI.
Choosing a Tool¶
| Tool | Use it when | Why |
|---|---|---|
| VS Code Extension | You are writing or debugging AmiScript and AMISQL in an editor | Completion, diagnostics, and breakpoints come from the running deployment rather than a separate grammar |
| Language and Debug Servers | You are enabling or securing the editor integration on a deployment | The LSP and DAP endpoints are what the extension connects to, and they are configured on the AmiCore side |
| Unit Testing | You want repeatable pass/fail on Center logic, locally or in CI | Each run uses an isolated clone, so no live data is touched and no feed, timer, or replication can flake a test |
| Center Debugger | You need to inspect server-side execution without an IDE | The command surface is driven from MCP or the admin console, and keeps working while the Center is frozen |
| Code Coverage | You need to know which paths your tests or real traffic exercise | Branch coverage catches untested arms that 100% line coverage hides |
The server-side tools share one engine. The Center debugger's per-statement hook is what the unit-test runner reuses to measure coverage, and the DAP server exposes that same stop-the-world debugger to your editor. Because the language and debug servers run inside AmiCore, what the IDE reports matches what the deployment actually does.
Prerequisites¶
- A running AmiCore instance with the relevant plugins enabled (see each page).
- VS Code 1.75+ for the extension.
- Java 17+ only for the extension's offline (sidecar) language mode, or when running a standalone language server without a live AmiCore.