Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • Corryvreckan Corryvreckan
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 40
    • Issues 40
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CorryvreckanCorryvreckan
  • CorryvreckanCorryvreckan
  • Issues
  • #40
Closed
Open
Issue created Nov 08, 2018 by Simon Spannagel@simonspaOwner

Add Test Cases and a CI Testing Stage

For every detector/DUT supported, we should add one test case with abbreviated data files, placed on the newly created EOS project space to be found at /eos/project/c/corryvreckan/. A script should be able to download these files and execute the framework with the corresponding configuration files.

The output checked should e.g. be the number of tracks found.

This way we can monitor that new additions or changes do not break compatibility with our existing setups and data sets.

Assignee
Assign to
Time tracking