Repository navigation
60 lines (52 loc) · 2.17 KB
/
Copy pathpython-app.yml
File metadata and controls
60 lines (52 loc) · 2.17 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
# This workflow will install Python dependencies, run tests and lint with a single version of Python
# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python
name: Python application
on:
push:
branches: [ "master" ]
pull_request:
branches: [ "master" ]
permissions:
contents: read
jobs:
build:
runs-on: ubuntu-latest
# the suite is run once per storage backend. A test that is about one of
# them is marked `@pytest.mark.backend(...)` and is skipped by the run
# for the other, so a single run has never been the whole suite: with
# only the default (YAML) job, every test of the HTTP tier - which is
# pinned to SQLite - was skipped and nothing here ever exercised it
strategy:
fail-fast: false
matrix:
backend: [yaml, sqlite]
name: build (${{ matrix.backend }})
steps:
- uses: actions/checkout@v4
- name: Set up Python 3.10
uses: actions/setup-python@v3
with:
python-version: "3.10"
- name: Install dependencies
run: |
python -m pip install --upgrade pip
pip install flake8 pytest
if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
# installs the package, which is what puts bgcserver, bgcclient and
# bgcobserver on the path. Without it tests/test_cli_installation.py
# skips and nothing here ever runs the commands a user runs
pip install -e '.[dev]'
- name: Lint with flake8
run: |
# stop the build if there are Python syntax errors or undefined names
flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
# exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
- name: Test with pytest
env:
# which backend this job is for. `tests/conftest.py` reads it to
# decide which pinned tests belong to this run, and the roles and
# the API server read it to decide what they store a game in
BOARD_GAME_BACKEND: ${{ matrix.backend }}
run: |
pytest -v