Skip to content
GitLab
Projects Groups 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
    • Contributors
    • Graph
    • Compare
  • 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
    • Infrastructure Registry
  • 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
  • #27
Closed
Open
Issue created Feb 02, 2021 by Simon Pastor@pastorsDeveloper

Plugtest 2021: MEC013 Location API using v1.1.1 schemas and endpoints, not v2.1.1

MEC013 Location API v2.1.1 is not fully supported by the MEC013 test suites

UELOCLOOK uses endpoint location/v2/users, and not location/v2/query/users UEINFOLOOK uses endpoint location/v2/users, and not location/v2/query/users RLOCLOOK uses endpoint location/v2/zones, and not location/v2/query/zones

All schemas for every test suites seem to use not named object, although the spec seemed to show the use of inline (named) objects. This result in validation to be missing one level of hierarchy (does not match the content of the file LocationAPI describe in the header which uses inline objects in its responses)

Note: Note that UEINFOSUB uses values instead of arrays as specified v2.1.1 in its default editable fields (interestRealm, userCriteria)

Edited Feb 02, 2021 by Simon Pastor
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking