Feat: initial testing setup

[lalver1]

Closes #6

This PR

• adds test dependencies
• configures VS Code for pytest
• creates a test file and a test that requests a /healthcheck endpoint from the app and asserts a 200 response code and "Healthy" response text. The endpoint is implemented as Django middleware.
• create a GitHub Actions workflow to run pytests on push and pull_request, upload coverage report, comment w/coverage report

The Pytest workflow is failing probably due to a pending python-coverage-comment-action-data branch.

[thekaveman]

The Pytest workflow is failing probably due to a pending python-coverage-comment-action-data branch.

This is probably related to GitHub Actions permissions somehow...

I feel like it should be able to create that branch? I can't remember what we did in the past, but I'm pretty sure I never created the branch by hand. The docs say

GitHub Actions will create this branch with initial data at the first run if it doesn't exist, and will independently commit to that branch after each commit to your default branch.

There's also this note in the docs: https://github.com/py-cov-action/python-coverage-comment-action?tab=readme-ov-file#setup

Please ensure that your .coverage file(s) is created with the option relative_files = true.

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
pems/core
middleware.py					19
Project Total

This report was generated by python-coverage-comment-action

[lalver1]

Ah, I had forgotten to configure coverage in pyproject.toml, looks like the GitHub Actions workflow runs now 😅

[thekaveman]

Looks great! I was able to run the tests locally in the devcontainer too.