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
  • #165
Closed
Open
Issue created Feb 24, 2021 by yaoyuy@yaoyuy

Using the same parameter when checking full size and Content-length SOL003 v2.6.1 VNFPackageManagementAPI

Same parameter is used to check for the file size and range size.and they can only be eqaul if the range size is same with the file size. eg. the file size is 51 and the request range is range :bytes=0-50 so the response in Content-Range will be bytes 0-50/51 and the Content-Length will be 51 too

Another situation is the file size is 1000 and the request range is range :bytes=0-50 so the response in Content-Range will be bytes 0-50/1000 and the Content-Length will be 51

The parameter used to be ${full_size} and ${length} but it is changed now.

Check HTTP Response Header Content-Range Is Present and Matches the requested range
    Log    Check Content-Range HTTP Header
    Should Contain    ${response['headers']}    Content-Range
    Should Be Equal As Strings    ${response['headers']['Content-Range']}    bytes ${range}/${full_length}
    Log    Header Content-Range is present
    
Check HTTP Response Header Content-Length Is Present and Matches the requested range length
    Log    Check Content-Length HTTP Header
    Should Contain    ${response['headers']}    Content-Length
    Should Be Equal As Integers    ${response['headers']['Content-Length']}    ${full_length}
    Log    Header Content-Length is present
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking