Skip to content
GitLab
Projects Groups Snippets
  • /
  • 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 17
    • Merge requests 17
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • NFV - Network Functions VirtualisationNFV - Network Functions Virtualisation
  • api-tests
  • Issues
  • #122
Closed
Open
Issue created Aug 13, 2020 by Frank Bryden@brydenf

[sol005robot] Logical inconsistency in NSLCM/IndividualNSInstance.robot

NSLCM/IndividualNSInstance.robot

The suite keyword Check resource existence is shown below (in the log.html output file). suiteSetup

The resource checked is at ns_instances/${nsInstanceId}, and the test is looking for a 200 response code, as the resource must exist.

However, at the end of the first test in the suite, POST Individual NSInstance - Method not implemented, a postcondition check for the non-existence of that same resource is made; pictured below. suiteCheck
This check is making a request against the same resource, but expecting a 404 this time.

If the suite setup succeeds, the test is run, but the response to that request cannot be 404.
If the suite setup fails, the test is not run.

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