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 4
    • Merge requests 4
  • 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
  • #68

Closed
Open
Created Jun 04, 2019 by pasricha@pasricha

SOL002/VNFIndicator-API/Subscriptions.robot and IndividualSubscription.robot failing due to Discrepency in the Specifications and the schema definition for VnfIndicatorSubscription object

A few test cases in SOL002/VNFIndicator-API/Subscriptions.robot and IndividualSubscription.robot are failing due to a mismatch in the Specifications document (gs_NFV-SOL002v020401p.pdf document, page 204) and the VnfIndicatorSubscriptions.schema.json & VnfIndicatorSubscription.schema.json schemas given in SOL002/VNFIndicator-API/schemas directory. As per Spec, the filter property in the VnfIndicatorSubscription is of type VnfIndicatorNotificationsFilter whereas in the schema definition it is defined to be of type VnfInstanceSubscriptionFilter

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