MEC Robot Test Suite issueshttps://forge.etsi.org/rep/mec/gs032p3-robot-test-suite/-/issues2021-02-18T17:20:02Zhttps://forge.etsi.org/rep/mec/gs032p3-robot-test-suite/-/issues/41Review the TPs and TCs on MEC 0132021-02-18T17:20:02ZMichele CarignaniReview the TPs and TCs on MEC 013https://forge.etsi.org/rep/mec/gs032p3-robot-test-suite/-/issues/38Plugtest 2021: Specification discussion: non existent attribute in a json bod...2021-02-26T20:19:05ZSimon PastorPlugtest 2021: Specification discussion: non existent attribute in a json body should be ignoredUsed as a placeholder for the specific issue below:
When receiving a json body and an attribute is not defined, the current expectation from the plugtest is to receive a code 400. Is a more appropriate action to ignore the unknown param...Used as a placeholder for the specific issue below:
When receiving a json body and an attribute is not defined, the current expectation from the plugtest is to receive a code 400. Is a more appropriate action to ignore the unknown parameter? This allows a less strict approach. It was not found in the spec what should be the behavior as a result of this situation. Need a clearer spec indication in order to standardized the implementations.https://forge.etsi.org/rep/mec/gs032p3-robot-test-suite/-/issues/25Templates for Notification requests are not resolved2021-02-03T10:53:46ZMichele CarignaniTemplates for Notification requests are not resolvedThe request object for Notification creation contains variables that should be resolved and substituted with the values inserted in variables.txt.
This is currently not supported. As a result, the body of the request contains the variab...The request object for Notification creation contains variables that should be resolved and substituted with the values inserted in variables.txt.
This is currently not supported. As a result, the body of the request contains the variable name, not the variable value.