enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-12-26 17:34:04 +03:00
Code Issues Projects Releases Wiki Activity
c8ea06c4a6
enso/tools/language-server/wstest
History
Jaroslav Tulach f53696eda4
sbt runEngineDistribution ...args... to build and execute the engine (#5609) 
Automating the assembly of the engine and its execution into a single task. If you are modifying standard libraries, engine sources or Enso tests, you can launch `sbt` and then just:
```
sbt:enso> runEngineDistribution --run test/Tests/src/Data/Maybe_Spec.enso
[info] Engine package created at built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev
[info] Executing built-distribution/enso-engine-...-dev/bin/enso --run test/Tests/src/Data/Maybe_Spec.enso
Maybe:  [5/5, 30ms]
- should have a None variant [14ms]
- should have a Some variant [5ms]
- should provide the `maybe` function [4ms]
- should provide `is_some` [2ms]
- should provide `is_none` [3ms]
5 tests succeeded.
0 tests failed.unEngineDistribution 4s
0 tests skipped.
```
the [runEngineDistribution](3a581f29ee/docs/CONTRIBUTING.md (running-enso)) `sbt` input task makes sure all your sources are properly compiled and only then executes your enso source. Everything ready at a single press of Enter.

# Important Notes
To debug in chrome dev tools, just add `--inspect`:
```
sbt:enso> runEngineDistribution --inspect --run test/Tests/src/Data/Maybe_Spec.enso
E.g. in Chrome open: devtools://devtools/bundled/js_app.html?ws=127.0.0.1:9229/7JsgjXlntK8
```
everything gets build and one can just attach the Enso debugger.
2023-02-16 21:37:12 +00:00
..
benchmarks sbt runEngineDistribution ...args... to build and execute the engine (#5609) 2023-02-16 21:37:12 +00:00
src Bump rustc to nightly-2023-01-12 (#4053) 2023-02-02 23:05:25 +00:00
Cargo.toml Dependency cleaning (#4092) 2023-01-27 23:39:37 +01:00
README.md Add Language Server benchmarking tool (#3578) 2022-07-22 14:12:52 +00:00

README.md

wstest

A tool for benchmarking the language server by sending a specified sequence of requests and waiting for expected responses. The results then can be analyzed with the logstat tool.

See benchmarks directory for examples.