mirror of
https://github.com/wger-project/wger.git
synced 2026-02-18 00:17:51 +01:00
Remove .travis.yml file
The tests are now performed via github actions
This commit is contained in:
@@ -1,2 +0,0 @@
|
||||
[run]
|
||||
omit = *migrations*
|
||||
54
.travis.yml
54
.travis.yml
@@ -1,54 +0,0 @@
|
||||
language: python
|
||||
dist: bionic
|
||||
|
||||
services:
|
||||
- postgresql
|
||||
|
||||
# Cache the pip files
|
||||
cache:
|
||||
directories:
|
||||
- $HOME/.cache/pip
|
||||
- $HOME/.nvm
|
||||
- node_modules
|
||||
- wger/node_modules
|
||||
|
||||
# Python versions to test
|
||||
python:
|
||||
- "3.6"
|
||||
- "3.7"
|
||||
- "3.8"
|
||||
|
||||
node_js: 10
|
||||
|
||||
env:
|
||||
- DB=postgresql
|
||||
- DB=sqlite
|
||||
|
||||
# Install the application
|
||||
install:
|
||||
# Install requirements
|
||||
- pip install -r requirements_dev.txt
|
||||
- python setup.py develop
|
||||
- cd wger
|
||||
- if [[ "$DB" = "postgresql" ]]; then pip install psycopg2; fi
|
||||
|
||||
# Setup application
|
||||
- if [[ "$DB" = "sqlite" ]]; then wger create-settings; fi
|
||||
- if [[ "$DB" = "postgresql" ]]; then wger create-settings --database-type postgresql; fi
|
||||
|
||||
# change back to the source folder
|
||||
- cd ..
|
||||
|
||||
# Create test databases
|
||||
before_script:
|
||||
- if [[ "$DB" = "postgresql" ]]; then psql -c 'DROP DATABASE IF EXISTS test_wger;' -U postgres; fi
|
||||
- if [[ "$DB" = "postgresql" ]]; then psql -c 'CREATE DATABASE test_wger;' -U postgres; fi
|
||||
|
||||
# Do the tests
|
||||
script:
|
||||
|
||||
# Regular application
|
||||
- coverage run --source='.' ./manage.py test --parallel
|
||||
|
||||
# Code coverage
|
||||
- coverage report
|
||||
@@ -142,8 +142,7 @@ Contributing
|
||||
people insist on rebasing before sending a pull request, it's not necessary.
|
||||
|
||||
* **Run the tests**: wger is proud to have a test coverage of over 90%. When you
|
||||
implement something new, don't forget to run the testsuite and write approriate
|
||||
tests for the new code. If you use github, configure the awesome Travis CI,
|
||||
there is already a .travis file in the sources.
|
||||
implement something new, don't forget to run the testsuite and write appropriate
|
||||
tests for the new code.
|
||||
|
||||
* **Code according to the coding style**: :ref:`codingstyle`
|
||||
|
||||
Reference in New Issue
Block a user