WSU-Software-Development-Club / WSU-Software-Development-Club/self-hosting
Add pytest with a /health test and GitHub Actions CI
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Why
Every PR should prove it didn't break the app. This issue sets up the testing and CI pattern that everyone else will copy.
Files to touch
backend/tests/test_health.py(new)backend/requirements-dev.txt(new) or addpytest+httpxtorequirements.txt.github/workflows/ci.yml(new)
Definition of done
-
pytestpasses locally with one test hitting/healthvia FastAPI'sTestClient - A GitHub Actions workflow runs
pyteston every pull request - The workflow shows a green check on this PR
Hints
No database is needed yet since /health doesn't touch Postgres. Start from the actions/setup-python starter workflow. FastAPI testing docs: https://fastapi.tiangolo.com/tutorial/testing/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the FastAPI app entry point and the actions/setup-python starter workflow, then create backend/tests/test_health.py, backend/requirements-dev.txt, and .github/workflows/ci.yml as described. Use FastAPI's TestClient to exercise /health without a database. Done means pytest passes locally and GitHub Actions runs it on every pull request with a green check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, github-actions, python
- Domain
- backend, ci-cd, testing
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 90/100