Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A api-tests
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • NFV - Network Functions Virtualisation
  • api-tests
  • Issues
  • #131

Closed
Open
Created Sep 10, 2020 by Frank Bryden@brydenf

NS Identifier Creation Notification/NS Identifier Deletion Notification schemas inverted

In SOL005\NSLifecycleManagement-API\NotificationEndpoint.robot, the tests NS Identifier Creation Notification and NS Identifier Deletion Notification have their schemas inverted. The creation test checks against the NsIdentifierDeletionNotification schema, whilst the Deletion test checks against the NsIdentifierCreationNotification schema.

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