ci: add test workflow

.github/workflows/test-package.yml

@@ -0,0 +1,29 @@
+name: Test Python package
+
+on:
+  push:
+    branches: [ "master" ]
+  pull_request:
+    branches: [ "master" ]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12"]
+
+    steps:
+    - uses: actions/checkout@v4
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: actions/setup-python@v3
+      with:
+        python-version: ${{ matrix.python-version }}
+    - name: Install Poetry
+      uses: snok/install-poetry@v1
+    - name: Install project
+      run: poetry install --no-interaction --with dev
+    - name: Test with pytest
+      run: poetry run pytest

README.md

@@ -2,7 +2,7 @@
 
 > the problem with doing weird metaprogramming shit is having to deal with *other people's weird metaprogramming shit*
 
-A tool that allows you to trace and modify the result of (almost) every single expression executed in a Python program.
+Trace and modify the result of (almost) every single expression executed in a Python program. WIP.
 
 ```python
 from maxray import transform, xray, maxray
@@ -39,5 +39,3 @@ show_multiply(
 The `*xray` decorators will recursively trace and patch every single callable they encounter until reaching either builtins, native, or generated code.
 
 The `ctx` argument contains context information about the location of the original source code, which may be useful to build editor/LSP integrations.
-
-WIP.

pyproject.toml

@@ -16,6 +16,9 @@ result = "^0.16.1"
 loguru = "^0.7.2"
 
 
+[tool.poetry.group.dev.dependencies]
+pytest = "^8.1.1"
+
 [build-system]
 requires = ["poetry-core"]
 build-backend = "poetry.core.masonry.api"