Skip to content

Commit 1ec7d23

Browse files
committed
more clarifications
1 parent a985c7f commit 1ec7d23

1 file changed

Lines changed: 9 additions & 2 deletions

File tree

README.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,10 @@ All the code that is new for this repository (e.g., the driver classes) is relea
2323
However, this repository contains as well sources from different open-source
2424
projects, each one with its own license, as clarified in more details beneath.
2525

26+
## Example
2627

28+
To see an example of using these drivers with EvoMaster to generate test cases, you can look at this [short video](https://youtu.be/3mYxjgnhLEo) (5 minutes).
29+
2730
## Current Case Studies
2831

2932
The projects were selected based on searches using keywords on GitHub APIs, using convenience sampling.
@@ -127,11 +130,15 @@ The script will issue error messages if any prerequisite is missing.
127130
Once the script is completed, all the SUTs will be available under the `dist` folder, and a `dist.zip` will be created as well.
128131
Note that here the drivers will be built as well besides the SUTs, and the SUT themselves will be instrumented by code manipulations (for white-box testing heuristics) of _EvoMaster_ (this is for JavaScript and .Net, whereas instrumentation for JVM is done at runtime, via an attached JavaAgent).
129132

133+
For running experiments with EvoMaster, you can also "start" each driver directly from an IDE (e.g., IntelliJ).
134+
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.
135+
For JavaScript, you need to use the files `em-main.js`.
130136

131-
For using EMB in other context, you can build (and install) each module separately, based on needs.
137+
138+
For using EMB in other contexts besides EvoMaster, you can build (and install) each module separately, based on needs.
132139
For example, a Maven module can be installed with:
133140

134-
``mvn clean package -DskipTests``
141+
``mvn clean install -DskipTests``
135142

136143
However, it is important to understand how this repository is structured, to be able to effectively navigate through it.
137144
Each folder represents a set of SUTs (and drivers) that can be built using the same tools.

0 commit comments

Comments
 (0)