1. 13 Apr, 2021 1 commit
  2. 15 Mar, 2021 14 commits
  3. 13 Mar, 2021 2 commits
    • Einar Uvsløkk's avatar
      Fix error in workout permissions · 7b0c8ee6
      Einar Uvsløkk authored
      During black box testing of FR5 (View Workout) an error related to
      workout permissions was discovered. Due to using wrong values when
      checking Coach visibility on workouts, coaches was not able to view
      workout details for their athletes.
      Unit tests are also updated to reflect the changes.
    • Einar Uvsløkk's avatar
      Add black box test for FR5 · ae8f0085
      Einar Uvsløkk authored
      Implement black box test for FR5 "View Workout" using Selenium.
  4. 12 Mar, 2021 1 commit
    • Einar Uvsløkk's avatar
      Fix the UserSerializer class · 46b009c0
      Einar Uvsløkk authored
      During black box testing of FR5 (View Workout) a bug in the class-level
      validation on the UserSerializer class was discovered. When accepting a
      coach offer, user validation would fail, complaining about the password
      being None.
      The changes made to the initial implementation is know mostly reverted.
      Class-level validation is removed in favour of field-level validation
      for the password field. The implementation of the password validation,
      however, remains the same.
      Additionally, default values for related required fields are know
      declared using the `extra_kwargs` attribute.
      Unit tests for the UserSerializer class is also updated, to reflect the
  5. 11 Mar, 2021 3 commits
  6. 09 Mar, 2021 8 commits
  7. 07 Mar, 2021 1 commit
  8. 06 Mar, 2021 4 commits
  9. 05 Mar, 2021 5 commits
    • Einar Uvsløkk's avatar
      Merge branch 'fix-pipeline' into 'master' · ba3a07be
      Einar Uvsløkk authored
      Make the pg_config available on test image
      See merge request !5
    • Einar Uvsløkk's avatar
    • Einar Uvsløkk's avatar
      Use psycopg2-binary to avoid building from source · aecc0b46
      Einar Uvsløkk authored
      The psycopg2 requirement got included in the requirements.txt file when
      django-heroku was added in commit 1667ceda, which in turn broke the CI
    • Einar Uvsløkk's avatar
      Setup continuous deployment to heroku · 1667ceda
      Einar Uvsløkk authored
      - Use django-heroku to configure backend for heroku
      - Use dj-database-url to configure database with DATABASE_URL
      - Add Procfile for backend
      - Add requirements.txt to repo root for heroku/python build
      - Move runtime.txt to repo root
      - Add Procfile for frontend
      - Add package.json to repo root for heroku/nodejs build
    • Einar Uvsløkk's avatar
      Fix invalid start byte in requirements.txt · 908dc731
      Einar Uvsløkk authored
      Using pipenv to install dependencies from requirements.txt resulted in
      the following error (pipenv install -r requirements.txt):
          Unexpected syntax in …/requirements.txt.
          Are you sure this is a requirements.txt style file?
          'utf-8' codec can't decode byte 0xff in position 0: invalid start byte
      Turns out the encoding of the file got messed up somehow!?
      The invalid start byte is caused by the <feff> character.
      Running file requirements.txt reveals:
          requirements.txt: Little-endian UTF-16 Unicode text, with CRLF line terminators
      Fixed by running:
          iconv -f utf-16 -t utf-8 requirements.txt -o requirements.txt.new
          dos2unix requirements.txt.new
          mv requirements.txt.new requirements.txt
  10. 04 Mar, 2021 1 commit