You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -170,14 +170,14 @@ In the built `dist` folder, the files will be organized as follows:
170
170
171
171
* For JVM: `<name>-sut.jar` will be the non-instrumented SUTs, whereas their executable drivers will be called `<name>-evomaster-runner.jar`.
172
172
Instrumentation can be done at runtime by attaching the `evomaster-agent.jar` JavaAgent. If you are running experiments with EvoMaster, this will be automatically attached when running experiments with `exp.py` (available in the EvoMaster's repository). Or it can be attached manually with JVM option `-Devomaster.instrumentation.jar.path=evomaster-agent.jar` when starting the driver.
173
-
* For NodeJS: under the folder `<name>` (for each NodeJS SUT), the SUT is available under `src`, whereas the instrumented version is under `build`.
173
+
* For NodeJS: under the folder `<name>` (for each NodeJS SUT), the SUT is available under `src`, whereas the instrumented version is under `instrumented`. If the SUT is written in TypeScript, then the compiled version will be under `build`.
174
174
* For .NET: currently only the instrumented version is available (WORK IN PROGRESS)
175
175
176
176
177
177
178
178
For running experiments with EvoMaster, you can also "start" each driver directly from an IDE (e.g., IntelliJ).
179
179
Each of these drivers has a "main" method that is running a REST API (binding on default port 40100), where each operation (like start/stop/reset the SUT) can be called via an HTTP message by EvoMaster.
180
-
For JavaScript, you need to use the files `em-main.js`.
180
+
For JavaScript, you need to use the files `em-main.js` under the `instrumented/em` folders.
181
181
182
182
183
183
@@ -198,6 +198,7 @@ Note: building a top-module will build as well all of its internal submodules.
198
198
Regarding JavaScript, unfortunately NodeJS does not have a good handling of multi-module projects.
199
199
Each SUT has to be built separately.
200
200
However, for each SUT, we put its source code under a folder called `src`, whereas all the code related to the drivers is under `em`.
201
+
Currently, both NodeJS `14` and `16` should work on these SUTs.
201
202
202
203
The driver classes for Java and .NET are called `EmbeddedEvoMasterController`.
203
204
For JavaScript, they are in a script file called `app-driver.js`.
0 commit comments