Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • N NGSI-LD 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
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CIM - Context Information Management
  • NGSI-LD Test Suite
  • Issues
  • #18
Closed
Open
Issue created Apr 02, 2022 by Benoit Orihuela@orihuelabMaintainer

Implement a specific comparison function for dates

Dates with milliseconds precision, but with millisecond value set to 0 (e.g., 2022-04-02T18:52:00.000Z) can be rendered as 2022-04-02T18:52:00.000Z or 2022-04-02T18:52:00Z. Both are correct and should be accepted when testing responses payloads.

As DeepDiff is already used in the test suite, a custom operator as described in https://zepworks.com/deepdiff/current/custom.html may be a good fit.

Assignee
Assign to
Time tracking