package testing
This commit is contained in:
+22
-2
@@ -136,8 +136,28 @@ npm --prefix tools/vscode-extension run compile
|
||||
PROMETEU_VSCODE_DEV_TEST=1 ./gradlew :prometeu-lsp:prometeu-lsp-v1:test --tests '*ExternalSourceDevelopmentHostTest' --console=plain
|
||||
```
|
||||
|
||||
Packaged Studio, installed distributions and installed JAR behavior were explicitly
|
||||
excluded by the user and were not validated. Development resource loading was tested.
|
||||
Packaged Studio was excluded from the initial acceptance above. On 2026-10-07,
|
||||
the user explicitly requested this additional validation. The existing
|
||||
`InstalledKnowledgeTest` now launches its isolated probe with the Java runtime
|
||||
from `installDist`, using distribution JARs plus test probe classes, with its working
|
||||
directory and projects outside the checkout. It asserts that the frontend and LSP
|
||||
bridge load from JARs and that SDK/core resources have `jar:` URLs.
|
||||
|
||||
The packaged gate passed:
|
||||
|
||||
```sh
|
||||
./gradlew :prometeu-app:installedKnowledgeTest --console=plain
|
||||
```
|
||||
|
||||
Besides reading the installed documentation and compiling its example, it verifies
|
||||
project-to-SDK, SDK-to-host and SDK-to-core definitions, matching declaration lines,
|
||||
exact SDK/core text against JAR bytes, read-only bundled descriptors, SDK hover and
|
||||
semantic tokens, and source revalidation after reconnect. The project contains only
|
||||
its original manifest and sources after navigation: no bundled source extraction.
|
||||
The first run caught an incorrect cursor position in the test fixture; calculating
|
||||
the position from the source fragment fixed the fixture. No production fix was needed.
|
||||
This is a packaged resource/backend gate; it does not launch the Studio desktop or
|
||||
repeat the VS Code UI checks against the installed process.
|
||||
|
||||
## Pitfalls
|
||||
|
||||
|
||||
Reference in New Issue
Block a user