Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • M MEC Robot Test Suite
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MEC - Multi-access Edge ComputingMEC - Multi-access Edge Computing
  • MEC Robot Test Suite
  • Issues
  • #24
Closed
Open
Issue created Jan 07, 2021 by Michele Carignani@carignaniContributor

Handle optionality for ProblemDetails presence and value check

The ProblemDetails data is set to be optional in some cases (see e.g. ETSI GS MEC 012, Table 7.3.3.1-2).

Currently the test suite requires the ProblemDetails data to always be present.

Expected behaviour

Allow the response to contain string or empty body, as well as the ProblemDetails data.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking