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

Better testing / Travis CI #41

Closed
jameslzhu opened this issue Feb 18, 2019 · 1 comment
Closed

Better testing / Travis CI #41

jameslzhu opened this issue Feb 18, 2019 · 1 comment

Comments

@jameslzhu
Copy link
Member

Testing is pretty much non-existent right now.

The current Travis-CI, configured with .travis.yml, does three things on a freshly installed Ubuntu 16.04 OS:

  • Install dependencies, with pipenv
  • Run SQL migrations (python manage.py migrate)
  • Run checks (python manage.py check)

And that's it. No tests on if anything actually works, no tests if urls hit the right pages, no checks if methods work, or really anything.

A good first start on this will be route tests: checking if a GET request to a specific url returns the right page. Beyond this we can check for db functionality on POST / GET requests, etc.

Relevant docs pages:

@jameslzhu jameslzhu added project and removed project labels Feb 27, 2019
@jameslzhu jameslzhu added this to Low priority in Beta issue triage Oct 21, 2019
@bri25yu bri25yu removed the medium label Sep 21, 2020
@bri25yu
Copy link
Contributor

bri25yu commented Apr 13, 2022

Closed by #447 and #443

@bri25yu bri25yu closed this as completed Apr 13, 2022
Beta issue triage automation moved this from Low priority to Closed Apr 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

2 participants