Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.webbeat.web
  • Issues
  • #128
Closed
Open
Issue created May 05, 2015 by Samuel GAIST@samuel.gaistOwner0 of 5 checklist items completed0/5 checklist items

Tests refactor

This is a set of things that should be done to improve testing:

  • Make use of the (overriding settings)[https://docs.djangoproject.com/en/1.7/topics/testing/tools/#overriding-settings] capabilities of django rather than have separated settings file
  • Rewrite tests so that common code/behavior is tested in one place and only module specific tests are written in submodule
  • Add tests that follow all possible code path (e.g. forking, creating a new version)
  • Add tests for variable fields query
  • Add website automated tests like suggested in #69
Assignee
Assign to
Time tracking