Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • otb otb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 196
    • Issues 196
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container 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
  • Main Repositories
  • otbotb
  • Issues
  • #2107
Closed
Open
Created Sep 28, 2020 by Julien Osman@julienosmanDeveloper1 of 3 tasks completed1/3 tasks

Add tests for reading and writing the Metadata

Currently, the tests run by the CI don't allow to check if there is a regression on the Metadata reading/writing process. With the coming of OTB version 8.0 freed from OSSIM, and the new Metadata architecture, we have no way to assess there is no regression, except by checking manually (see this exemple).

We should modify the script of image comparison used in the tests to compare the output to the baseline, so it also checks the metadata. That would mean updating a big part of the baseline, which is a lot of work.

To avoid this big update of the baseline, we could identify some common use-cases that need to be tested, and activate the metadata checking only for this cases. That way, we could cover the Metadata reading/writing process with a small change in the baseline.

  1. Implement metadata checking mechanism, test it on some basic applications. (5pts)
  2. Chose the applications and filters that are relevant for testing.
  3. Set up the tests for theses applications.
Edited Oct 27, 2020 by Cédric Traizet
Assignee
Assign to
Time tracking