Add GitHub workflow to run pytest #58
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #49
Add GitHub Actions Workflow for Running Tests
Summary
This PR introduces a GitHub Actions workflow to automatically run tests on every push to the
mainbranch and for every pull request. The workflow runs tests on Python 3.11 and 3.12 usingpytest.Changes Introduced
Run Testsworkflow in.github/workflows/test.yml.ubuntu-latest.uv.pytest.Required GitHub Secrets
To ensure the tests can access the required resources, these secrets must be set in your GitHub repository:
Gradient Storage
R2_GRADIENTS_ACCOUNT_IDR2_GRADIENTS_BUCKET_NAMER2_GRADIENTS_READ_ACCESS_KEY_IDR2_GRADIENTS_READ_SECRET_ACCESS_KEYR2_GRADIENTS_WRITE_ACCESS_KEY_IDR2_GRADIENTS_WRITE_SECRET_ACCESS_KEYDataset Storage
R2_DATASET_ACCOUNT_IDR2_DATASET_BUCKET_NAMER2_DATASET_READ_ACCESS_KEY_IDR2_DATASET_READ_SECRET_ACCESS_KEYR2_DATASET_WRITE_ACCESS_KEY_IDR2_DATASET_WRITE_SECRET_ACCESS_KEYOnce these secrets are in place, the workflow will install dependencies and run tests against the specified environments.