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 0
    • Merge requests 0
  • 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
  • #100
Closed
Open
Issue created Jun 02, 2020 by raducc@raducc

Assignment of response variable @ vs $ in VnfLcmMntOperationKeywords and NSLCMOperationKeywords

Please check the correct assignment of response variable in keywords robot files.

https://forge.etsi.org/rep/nfv/api-tests/blob/2.6.1-fix-plu/SOL003/VNFLifecycleManagement-API/VnfLcmMntOperationKeywords.robot

Set Global Variable @{response} ${outputResponse}

vs

Set Global Variable ${response} ${outputResponse}

Both forms are used in keyword files which misleads an NFVO solution.

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