Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
P PyNEMO
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 37
    • Issues 37
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • thopri
  • PyNEMO
  • Issues
  • #10

Closed
Open
Created May 29, 2019 by thopri@thopriMaintainer

Unit Testing for the code

Created by: jdha

Write a series of unit / benchmarking tests to check updates do not break break the code and performance is not hindered.

Unit tests: e.g. set all temperatures = 25, salinity = 35 to check interpolation

Benchmarking: Simple AMM7 tests (with standard results on a thredds server) to check updates haven't broken the code

Need to come up with a list.

Assignee
Assign to
Alpha (0.1) release
Milestone
Alpha (0.1) release (Past due)
Assign milestone
Time tracking