Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • seamcat seamcat
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 119
    • Issues 119
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • SEAM
  • seamcatseamcat
  • Issues
  • #29
Closed
Open
Issue created May 29, 2020 by Zeljko Tabakovic@zeljko.tabakovicMaintainer

Release check and unit tests

To define a methodology for checks to be applied before agreeing each release.

Increase the number of automatic tests within the code to prevent that any new changes to the code affect other parts of the code resulting in bugs that are discovered only after a release.

This will increase the robustness of the tool and the confidence of the users in new versions.

This relates to ID 1 in Roadmap for SEAMCAT development in 2020 which is identified as priority task by WGSE. Task is moved from Jira.

Edited Jul 05, 2020 by Zeljko Tabakovic
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking