Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E elsa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 51
    • Issues 51
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 20
    • Merge requests 20
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • IPIP
  • elsa
  • Issues
  • #20
Closed
Open
Issue created Oct 29, 2019 by Tobias Lasser@lasserOwner

Add TEMPLATE_TEST_CASE to our tests to improve function coverage

Currently, most tests are a simple SCENARIO that tests the templated code only for real_t as template argument. We should cover the other relevant types too, e.g. using TEMPLATE_TEST_CASE.

Typically, this type list is: float, double, std::complex<float>, std::complex<double> (except in some cases where complex numbers do not make sense). For DataContainer there is also index_t.

Assignee
Assign to
Time tracking

LRZ Homepage | Datenschutz | Dokumentation und Betriebsbedingungen | Impressum