DC and CI tweaks

.devcontainer/devcontainer.json

@@ -35,7 +35,8 @@
 					"editor.formatOnSave": true,
 					"editor.codeActionsOnSave": {
 						"source.fixAll": true
-					}
+					},
+					"editor.defaultFormatter": "ms-python.black-formatter"
 				},
 				"python.formatting.provider": "black",
 				"files.exclude": {
@@ -49,6 +50,7 @@
 			"extensions": [
 				"ms-python.python",
 				"ms-python.vscode-pylance",
+				"ms-python.black-formatter",
 				"charliermarsh.ruff",
 				"ms-azuretools.vscode-bicep",
 				"mtxr.sqltools",

.github/workflows/check.yaml

@@ -39,7 +39,7 @@ jobs:
             DBPASS: postgres
             SECRET_KEY: django-insecure-key-${{ github.run_id }}-${{ github.run_attempt }}
           run: |
-            python3 -m pytest
+            python3 -m pytest --cov-report=xml:coverage.xml --junitxml=pytest.xml
         - name: Pytest coverage comment
           uses: MishaKav/pytest-coverage-comment@main
           with:

pyproject.toml

@@ -14,7 +14,7 @@ exclude = '''
 '''
 
 [tool.pytest.ini_options]
-addopts = "-ra --cov=src --cov-report=xml:coverage.xml --junitxml=pytest.xml"
+addopts = "-ra --cov=src"
 pythonpath = ["src"]
 python_files = ["tests.py"]
 env_override_existing_values = 1

src/quizsite/settings.py

@@ -38,6 +38,8 @@ SECRET_KEY = env("SECRET_KEY")
 
 # SECURITY WARNING: don't run with debug turned on in production!
 DEBUG = env("DEBUG")
+# This allows us to use the VS Code debugger to break on exceptions
+DEBUG_PROPAGATE_EXCEPTIONS = env("DEBUG")
 
 # Configure the domain name using the environment variable
 # that Azure automatically creates for us.