feat: mqtt event handler

.eslintrc

@@ -1,9 +1,7 @@
-
 env:
   node: true
   es6: true
-  mocha: false
-
+  mocha: true
 
 plugins:
   - sonarjs
@@ -16,9 +14,7 @@ extends:
   - plugin:security/recommended
 
 parserOptions:
-  ecmaVersion: 2018
-  ecmaFeatures:
-    experimentalObjectRestSpread: true
+  ecmaVersion: 2020
 
 rules:
   # Ignore Rules

README.md

@@ -1,14 +1,19 @@
-# AsyncApi Performance Tester
+# AsyncApi Simulator
 ___
 
+ In development
+
+---
+
 Ever wondered what it would feel like your application to 
 be the center of interest?
 
 Does it seem distant or difficult to switch from development mode
 to production mode?
 
-#### Define and simulate high traffic
-#### scenarios for your app and create statistics.
+#### Define and simulate high traffic scenarios for your app and create statistics.
+
+
 
 Usage
 
@@ -17,6 +22,48 @@ simulator -f ./my_api.yaml -s ./scenario.yaml
 simulator -f ../subdirectory/my_api.json -s ./scenario.json
 ```
 
+Run sample application with --gameProcessor or 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
+```
+
+
+
+### Cli
+
+```
+Options:
+  -v                     async-api performance tester cli version
+  -f, --filepath <type>  The filepath of a async-api specification yaml or json asyncApiF
+  -s, --scenario <type>  The filepath of a AsyncApi File defining a scenario based on the spec.
+  -b, --basedir <type>   The basePath from which relative paths are computed.
+                         Defaults to the root directory of the project.
+  -h, --help             display help for command
+
+
+```
+
+### Supported Protocols
+
+- mqtt
+
+### AsyncApi File
+
+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.
+
+
+
+### Scenario File
+
+Here with the plot-{id} (where id is the same as the x-plot: {id} in the field you specified in the async api 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.
+
 
 
 

example-projects/game-processor/asyncapi.yaml

@@ -1,66 +1,67 @@
 asyncapi: 2.0.0
-info: 
+info:
   title: "Processor"
-  version: "0.0.1"  
+  version: "0.0.1"
   license:
     name: Apache 2.0
     url: https://www.apache.org/licenses/LICENSE-2.0
-servers: 
-  local: 
+servers:
+  local:
     url: "0.0.0.0:1883"
-    description: "Development server",
+    description: "Development server"
     protocol: "mqtt"
 defaultContentType: application/json
-channels: 
+channels:
   game/server/{serverId}/events/player/{playerId}/item/{itemId}/pickup:
+    x-plot: 1
     description: Channel used when a player picks up an item in-game
     parameters:
-      serverId: 
-        $ref: "./AsyncAPI/components/Parameters.yaml#/serverId"
-      playerId: 
-        $ref: "./AsyncAPI/components/Parameters.yaml#/playerId"
-      itemId: 
-        $ref: "./AsyncAPI/components/Parameters.yaml#/itemId"
-    publish: 
+      serverId:
+        $ref:  "./example-projects/game-processor/AsyncAPI/components/Parameters.yaml#/serverId"
+      playerId:
+        $ref: "./example-projects/game-processor/AsyncAPI/components/Parameters.yaml#/playerId"
+      itemId:
+        $ref: "./example-projects/game-processor/AsyncAPI/components/Parameters.yaml#/itemId"
+    publish:
       message:
-        $ref: './AsyncAPI/components/messages/PlayerItemPickup.yaml'
+        $ref: './example-projects/game-processor/AsyncAPI/components/messages/PlayerItemPickup.yaml'
   game/server/{serverId}/events/player/{playerId}/connect:
     description: Channel used when a player joins (connect to) the game server
     parameters:
-      serverId: 
-        $ref: "./AsyncAPI/components/Parameters.yaml#/serverId"
-      playerId: 
-        $ref: "./AsyncAPI/components/Parameters.yaml#/playerId"
-    publish: 
+      serverId:
+        $ref: "./example-projects/game-processor/AsyncAPI/components/Parameters.yaml#/serverId"
+      playerId:
+        $ref: "./example-projects/game-processor/AsyncAPI/components/Parameters.yaml#/playerId"
+    publish:
       message:
-        $ref: './AsyncAPI/components/messages/PlayerConnected.yaml'
+        $ref: './example-projects/game-processor/AsyncAPI/components/messages/PlayerConnected.yaml'
   game/server/{serverId}/events/player/{playerId}/disconnect:
     description: Channel used when a player leaves (disconnects from) the game server
     parameters:
-      serverId: 
-        $ref: "./AsyncAPI/components/Parameters.yaml#/serverId"
-      playerId: 
-        $ref: "./AsyncAPI/components/Parameters.yaml#/playerId"
-    publish: 
+      serverId:
+        $ref: "./example-projects/game-processor/AsyncAPI/components/Parameters.yaml#/serverId"
+      playerId:
+        $ref: "./example-projects/game-processor/AsyncAPI/components/Parameters.yaml#/playerId"
+    publish:
       message:
-        $ref: './AsyncAPI/components/messages/PlayerDisconnected.yaml'
-  game/server/{serverId}/events/player/{playerId}/chat: 
+        $ref: './example-projects/game-processor/AsyncAPI/components/messages/PlayerDisconnected.yaml'
+  game/server/{serverId}/events/player/{playerId}/chat:
     description: Channel used when a player writes something in chat
     parameters:
-      serverId: 
-        $ref: "./AsyncAPI/components/Parameters.yaml#/serverId"
-      playerId: 
-        $ref: "./AsyncAPI/components/Parameters.yaml#/playerId"
-    publish: 
+      serverId:
+        $ref: "./example-projects/game-processor/AsyncAPI/components/Parameters.yaml#/serverId"
+      playerId:
+        $ref: "./example-projects/game-processor/AsyncAPI/components/Parameters.yaml#/playerId"
+    publish:
       message:
-        $ref: './AsyncAPI/components/messages/PlayerUsedChat.yaml'
-  game/server/{serverId}/events/player/{playerId}/hit: 
+        $ref: './example-projects/game-processor/AsyncAPI/components/messages/PlayerUsedChat.yaml'
+  game/server/{serverId}/events/player/{playerId}/hit:
     description: Channel used when a player hit another player in-game
     parameters:
-      serverId: 
-        $ref: "./AsyncAPI/components/Parameters.yaml#/serverId"
-      playerId: 
-        $ref: "./AsyncAPI/components/Parameters.yaml#/playerId"
-    publish: 
+      serverId:
+        $ref: "./example-projects/game-processor/AsyncAPI/components/Parameters.yaml#/serverId"
+      playerId:
+        $ref: "./example-projects/game-processor/AsyncAPI/components/Parameters.yaml#/playerId"
+    publish:
       message:
-        $ref: './AsyncAPI/components/messages/PlayerHit.yaml'
+        $ref: './example-projects/game-processor/AsyncAPI/components/messages/PlayerHit.yaml'

example-projects/game-processor/config.js

@@ -8,5 +8,5 @@ module.exports = {
     mongodbPlayerHitCollection: "playerHit",
     mongodbDisconnectsCollection: "disconnects",
     mongodbChatCollection: "chat",
-    mqttHost: process.env.mqttHost || "tcp://0.0.0.0:1883"
-};
+    mqttHost: process.env.mqttHost || "tcp://0.0.0.0:1883"
+};

example-projects/game-processor/index.js

@@ -22,7 +22,7 @@ async function saveToCollection(persistentLogId, collection, data) {
 }
 /**
  * Short code for matching simple wildcards for topic and parameter separation
- * 
+ *
  * https://stackoverflow.com/a/32402438/6803886
  */
 function matchRuleShort(str, rule) {
@@ -72,7 +72,6 @@ async function start() {
     console.log(`Got message on topic ${topic}`)
     // message is Buffer
     const parsedMessage = JSON.parse(message.toString())
-
     // Naive approach to finding parameters, but it will have to do for now.
     const topicSplit = topic.split('/')
     if (matchRuleShort(topic, 'game/server/*/events/player/*/chat')) {

example-projects/game-processor/scenario.yaml

@@ -0,0 +1,11 @@
+version: 0.0.1
+plot-1:
+  eps: 1
+  priority: 2
+  payload:
+    test:
+      subtest: '2'
+  parameters:
+    serverId: '1'
+    playerId: '5'
+    itemId: '3'