Merge branch '44-add-python-testing-job-to-the-hub' into 'latest'

# 🐍 Python Testing

## Description

Allow you to launch unit tests from your python project. The default variables will use `pipenv` and `pytest` to launch the tests, but you're welcome to override them as you want.

## How to use it

1. Prepare your project with unit tests to run in a separate directory: [pytest usage](https://docs.pytest.org/en/2.8.7/usage.html)

2. Prepare a Pipfile for pipenv to install any python dependencies your project may have: [Pipfile for pipenv](https://pipenv-fork.readthedocs.io/en/latest/basics.html), including your test framework which is chosen by the `TEST_FRAMEWORK` [variable](#Variables)

3. Add the corresponding URL to your `.gitlab-ci.yml` file (see [Getting

   started](/getting-started)). Example:

    ```yaml

    include:

      - remote: 'https://jobs.go2scale.io/python_test.yml'

    ```

4. If you need to customize the job (stage, variables, ...) 👉 check the [jobs

   customization](/getting-started/#jobs-customization)

5. Well done, your job is ready to work ! 😀

## Job details

* Job name: `python_test`

* Docker image:

[`python:3.7`](https://hub.docker.com/r/_/python)

* Default stage: `static_tests`

* When: `always`

!!! note

    We are not using an [alpine linux](https://alpinelinux.org/) docker image in order to improve speed over ressource efficiency. Alpine linux is using musl-libc and not glibc, so it can't use the python [wheels](https://pythonwheels.com/) with pip to get compiled dependencies while seting up your environment, and have to download and compile from source those libraries. As speed is the real issue that CI can have when building complex systems, we decided to use the general docker image of `python:3.7` based on Debian. You can see the explanation at this [link](https://pythonspeed.com/articles/alpine-docker-python/#:~:text=Don't%20use%20Alpine%20Linux,choosing%20a%20good%20base%20image).

### Variables

| Name | Description | Default |

| ---- | ----------- | ------- |

| `APT_PACKAGES` | Packages that need to be installed | ` ` |

| `PYTHON_SETUP` | Bash commands to setup your python environment | `pip install pipenv; pipenv --bare install --dev` |

| `VENV` | Command to launch your testing environment | `pipenv run` |

| `TEST_FRAMEWORK` | Command to launch your testing framework | `pytest` |

| `OPTIONS` | Options to add to your testing framework | ` ` |

| `TEST_PATH` | Path to test folder | `/tests/unit` |

#### Changing the test framework

If you want for example to change your test framework from pytest to nosetests, you just have to override the `TEST_FRAMEWORK` variable as such in your `gitlab-ci.yml`, after including the job:

```yaml

python_tests:

  variables:

    TEST_FRAMEWORK: "nosetests"

```

## Versions

* **Latest** (current -> `2020-09-09_1`) : `https://jobs.go2scale.io/latest/python_test.yml`

* **Tag `2020-09-09_1`** (initial version) : `https://jobs.go2scale.io/2020-09-09_1/python_tests.yml`

# Job from go2scale hub --> hub.go2scale.io

python_test:

  stage: static_tests

  image: python:3.7

  variables:

    # Dependencies variables

    APT_PACKAGES: ""

    PYTHON_SETUP: "pip install pipenv; pipenv --bare install --dev"

    # Running variables 

    VENV: "pipenv run"

    TEST_FRAMEWORK: "pytest"

    OPTIONS: ""

    TEST_PATH: "tests/unit"

  before_script:

    - if ! [ -z "${APT_PACKAGES}" ]; then apt install -y ${APT_PACKAGES}; fi

    - eval ${PYTHON_SETUP}

  script:

    - ${VENV} ${TEST_FRAMEWORK} ${OPTIONS} ${TEST_PATH}

 No newline at end of file