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
  • #44

Closed
Open
Created Jan 17, 2020 by thopri@thopriMaintainer

Design testing regime

Created by: thopri

At the moment there is no clear testing cycle with PyNEMO, new bits of code are tested but the impact on old functionality is not fully checked. Long term using Travis CI to test when building will be implemented but for now a testing check list and python script will be created.

The check list will check certain functions or "routes" through the module, test the GUI and settings editor works etc. The script will test the output, such as confirming constant temp and salinity results in constant temp and salinity out.

These tests and checklists will be used before each release and merge into master.

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