Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #11141

Closed (moved)
Open
Opened Mar 05, 2014 by Trac@tracbot

Create unit-tests for weather components

In order to make current work and future integration as stable and seamless as possible, we should cover all code by unit-tests.

To start with, we could begin with a test suite containing all re-written components and move towards full coverage once the integration is stable.

Unless any team member has prior experience with testing Python/Django applications ([[https://nose.readthedocs.org/en/latest/|Nose]] looks promising), I suggest we stick with Python's [[http://docs.python.org/2/library/unittest.html|unittest]]-module for the following reasons: a) preferred way of [Django] b) part of batteries-included Python - no extra installation necessary, which lends itself well to portability

Measuring code coverage and performing CI could be possible next steps.

Trac:
Username: baumanno

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#11141