Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • M MEC Robot Test Suite
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MEC - Multi-access Edge ComputingMEC - Multi-access Edge Computing
  • MEC Robot Test Suite
  • Issues
  • #34
Closed
Open
Issue created Feb 10, 2021 by Simon Pastor@pastorsDeveloper

Plugtest 2021: MEC013: ClientCorrelator error in UELOCSUB

TEST UELOCSUB 001 OK

There seem to be a check for an optional parameter, clientCorrelator, but it seems not defined somehow so it cannot look at the response and do the comparison. The parameter is an optional parameter, not sure if this is where the problem is, but cannot understand why this error pops out. It seem to be defined properly in the schema....

KEYWORD BuiltIn . Exit For Loop If ${item[${json_field}]} == ${json_value}
Documentation:	
Stops executing the enclosing for loop if the condition is true.

Start / End / Elapsed:	20210210 16:49:11.827 / 20210210 16:49:11.831 / 00:00:00.004
16:49:11.828	**FAIL	Resolving variable '${item[clientCorrelator]}' failed: NameError: name 'clientCorrelator' is not defined	**
16:49:11.826	TRACE	Arguments: [ ${expr}={'address': 'acr:10.0.0.1', 'callbackReference': {'notifyURL': 'http://clientApp.example.com/location_notifications/123456'}, 'clientCorrelator': '0125', 'resourceURL': 'http://ourserver/simon/location/v2/subscriptions/userTracking/4', 'userEventCriteria': ['Transferring']} | ${json_field}='clientCorrelator' | ${json_value}='0125' ]
Edited Feb 15, 2021 by Michele Carignani
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking