Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • vlbi_monitor vlbi_monitor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • radiolab
  • vlbi_monitorvlbi_monitor
  • Issues
  • #11

Closed
Open
Created Apr 11, 2016 by Harm Munk@harmmOwner

Test Plan for the VM

We need a test plan for the VM, that at least includes the following items (from an email by Pim Schellart):

  1. Exercise and audit all security paths in the code.
  2. Check for thread safety and fix any issues with that.
  3. Try an extensive run locally with multiple people viewing and chatting all the time and fix any issues that come up.
  4. Check for data integrity (ensure that everything actually arrives).
  5. Test as many failure modes as possible (e.g. database crashing, client sending bad request, client cutting off half way through transaction, etc.)
Assignee
Assign to
Time tracking