Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ion ion
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 86
    • Issues 86
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • redox-osredox-os
  • ionion
  • Issues
  • #420
Closed
Open
Issue created Jul 16, 2017 by Michael Aaron Murphy@mmstickMaintainer

testing: Increase Test Unit Coverage

We should perform an extensive code review at some point as we near a stable release, and create tests everywhere where possible (likely refactoring with closures to increase the test-ability of certain functions). When we are ready to do this, we should make a list of all the source files in the codebase, and then one by one review, test, and check that file off the list.

Edited Jun 01, 2021 by matu3ba
Assignee
Assign to
Time tracking