Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write Tests For Each Model #89

Open
6 tasks
govindrai opened this issue May 7, 2019 · 0 comments
Open
6 tasks

Write Tests For Each Model #89

govindrai opened this issue May 7, 2019 · 0 comments
Assignees
Labels
testing Used to denote tickets related to our test-suite

Comments

@govindrai
Copy link
Owner

govindrai commented May 7, 2019

Currently we have 0 tests. What i've come to realize is that tests are amazingly useful when you come back to stale code and have to relearn a lot of the codebase and when you start making changes you could easily break other parts of the codebase. I am afraid of how my changes will affect the rest of the codebase, but since we don't have tests, we don't have a choice.

We need to write tests (both unit and integration) for this application before we release it as future maintainers would probably have a very tough time with changes after we drop from the project. Currently we only have 6 models so this shouldn't be hard. Once we come up with a framework, it should be some hard labor and we could probably write up the application within two weeks.

Conditions of Satisfaction
Unit and Integration tests for the following models:

  • Activity
  • Challenge
  • Family
  • Participant
  • Point
  • User
@govindrai govindrai added the testing Used to denote tickets related to our test-suite label May 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing Used to denote tickets related to our test-suite
Projects
None yet
Development

No branches or pull requests

2 participants