Currently we have some tests validating requests, specifically for mef_eline, but we don't have much coverage about the expected response, that front-end also relies, since we're upgrading implementation details we'll need this e2e to ensure that no regression happens. For instance, here's an invalid payload for POST /api/kytos/mef_eline/v2/evc/, we should assert this response structure.
{
"code": 400,
"description": "The request body contains invalid API data. 1 is not of type 'string' for field uni_a/interface_id.",
"name": "Bad Request"
}
Currently we have some tests validating requests, specifically for mef_eline, but we don't have much coverage about the expected response, that front-end also relies, since we're upgrading implementation details we'll need this e2e to ensure that no regression happens. For instance, here's an invalid payload for
POST /api/kytos/mef_eline/v2/evc/
, we should assert this response structure.