feat: Use Gemini to set-up the basics of tests for our python cli

.github/workflows/python-tests.yml

@@ -0,0 +1,30 @@
+name: Python Tests
+
+on:
+  pull_request:
+    branches:
+      - main
+      - master
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.8", "3.9", "3.10"]
+
+    steps:
+      - uses: actions/checkout@v3
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v4
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install dependencies
+        run: |
+          cd ./unix
+          python -m pip install --upgrade pip
+          pip install -r requirements.txt
+          pip install -r dev-requirements.txt
+      - name: Test with pytest
+        run: |
+          pytest

.gitignore

@@ -1,2 +1,3 @@
 .DS_Store
 .vscode/
+*.pyc

unix/CONTRIBUTING.md

@@ -43,6 +43,22 @@ We use the following tools:
   src/machine_stats/*` or `pipenv run pylint src`)
 * `bump2version` for version bumps (`pipenv run bump2version`)
 
+### Testing
+
+We use `pytest` for testing. Test files are located in the `tests/` directory and should be named with a `test_` prefix (e.g., `test_my_feature.py`).
+
+To run the tests, use the following command:
+
+```console
+pytest
+```
+
+or
+
+```console
+pipenv run pytest
+```
+
 ### How to release a new Machine Stats version
 
 To deploy a new version of Machine Stats, you will need to create a release. The steps are pretty simple, You can find Github's instruction [here](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release).

unix/Pipfile

@@ -18,6 +18,8 @@ twine = "*"
 wheel = "*"
 build = "*"
 bump2version = "*"
+pytest = "*"
+pytest-mock = "*"
 
 [scripts]
 stats = "machine_stats"

unix/dev-requirements.txt

@@ -63,3 +63,5 @@ webencodings==0.5.1
 wheel==0.38.4
 wrapt==1.14.1; python_version < '3.11'
 zipp==3.11.0; python_version < '3.10'
+pytest
+pytest-mock