The official application for simulating scenarios
-
Command line library and desktop application for generating asynchronous traffic.
-
Visualize your asyncApi files and test your asynchronous networks.
This package is under development and it has not reached version 1.0.0 yet, which means its API might get breaking changes without prior notice. Once it reaches its first stable version, we'll follow semantic versioning.
Usage
npm run desktop
simulator -f ./my_api.yaml -s ./scenario.yaml
simulator -f ../subdirectory/my_api.json -s ./scenario.json
Run sample application by specifying the corresponding AsyncApi and scenario files.
simulator -f ./example-projects/game-processor/asyncapi.yaml -s ./example-projects/game-processor/scenario.yaml
or
simulator -b ../ -f ./simulatorFolder/example-projects/game-processor/asyncapi.yaml -s ./simulatorFolder/example-projects/game-processor/scenario.yaml
Options:
-v AsyncApi simulator cli version.
-f, --filepath <type> The filepath of a AsyncAPI document, as either yaml or json file.
-s, --scenario <type> The filepath of a json or yaml file which defines a scenario based on the spec.
-b, --basedir <type> The basePath from which relative paths are computed.
Defaults to the directory where simulator.sh resides. (default: "./").
-h, --help Display help for flags and commands.
- mqtt
The file where the api you want to test is defined. By specifying the x-plot: {id} field under a channel will automatically make the channel available for sending requests.
Here with the plot-{id} (where id is the same as the x-plot: {id} in the field you specified in the AsyncAPI channel) field you:
- Connect your AsyncApi and scenario File.
- Specify the parameters for each channel and have the options for them to be randomly generated.
- Specify the payload you want to send.
Read CONTRIBUTING guide.
Thanks goes to these wonderful people (emoji key):
NektariosFifes 💻 📖 🤔 🚧 |
Jonas Lagoni 📖 👀 🧑🏫 💡 |
This project follows the all-contributors specification. Contributions of any kind welcome!