Lars/shinkan-jinkendo
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Update pytest configuration and documentation for training planning integration
All checks were successful
Deploy Development / deploy (push) Successful in 38s
Details
Test Suite / pytest-backend (push) Successful in 37s
Details
Test Suite / lint-backend (push) Successful in 0s
Details
Test Suite / build-frontend (push) Successful in 13s
Details
Test Suite / k6 /health Baseline (push) Successful in 33s
Details
Test Suite / playwright-tests (push) Successful in 1m8s
Details

Browse Source 
- Enhanced the pytest workflow in `.gitea/workflows/test.yml` to include `TRAINING_PLANNING_INTEGRATION` for improved testing against the PostgreSQL database.
- Updated `pytest.ini` to clarify integration marker usage, specifying both `ACCESS_LAYER_INTEGRATION` and `TRAINING_PLANNING_INTEGRATION`.
- Revised documentation in `test_training_planning_sections_integration.py` to provide clearer activation instructions for local and CI environments.
This commit is contained in:
Lars 2026-05-14 22:35:12 +02:00
parent ae51d201bc
commit 0d34c0a73d
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.gitea/workflows/test.yml
View File

@ -10,7 +10,7 @@ on:
types: [completed] types: [completed]
jobs: jobs:
# Wie Mitai-Jinkendo: pytest im laufenden backend-Container (Python aus Image, gleiche DB wie Deploy). # Pytest im laufenden backend-Container; ACCESS_LAYER + TRAINING_PLANNING Integration gegen dieselbe PostgreSQL wie Deploy (Schema via Container-Start migriert).
pytest-backend: pytest-backend:
if: ${{ github.event_name != 'workflow_run' || github.event.workflow_run.conclusion == 'success' }} if: ${{ github.event_name != 'workflow_run' || github.event.workflow_run.conclusion == 'success' }}
runs-on: ubuntu-latest runs-on: ubuntu-latest
@ -39,7 +39,7 @@ jobs:
cd /app && cd /app &&
ACCESS_LAYER_STRICT=1 python scripts/check_access_layer_hints.py && ACCESS_LAYER_STRICT=1 python scripts/check_access_layer_hints.py &&
python scripts/security_release_checks.py && python scripts/security_release_checks.py &&
ACCESS_LAYER_INTEGRATION=1 SKIP_DB_MIGRATE=1 python -m pytest tests -m 'not slow' -ra -vv --tb=short ACCESS_LAYER_INTEGRATION=1 TRAINING_PLANNING_INTEGRATION=1 SKIP_DB_MIGRATE=1 python -m pytest tests -m 'not slow' -ra -vv --tb=short
" "
lint-backend: lint-backend:

2
backend/pytest.ini
View File

@ -6,5 +6,5 @@ python_functions = test_*
addopts = -q --tb=short addopts = -q --tb=short
markers = markers =
smoke: Schnelle Kern-Regression. smoke: Schnelle Kern-Regression.
integration: PostgreSQL-Mandanten-Integration (ACCESS_LAYER_INTEGRATION=1). integration: PostgreSQL-Integration (z. B. ACCESS_LAYER_INTEGRATION=1, TRAINING_PLANNING_INTEGRATION=1).
slow: Lange/schwere Tests; in CI wie Mitai-Jinkendo ausgeschlossen (Auswahl: not slow). slow: Lange/schwere Tests; in CI wie Mitai-Jinkendo ausgeschlossen (Auswahl: not slow).

6
backend/tests/test_training_planning_sections_integration.py
View File

@ -1,9 +1,9 @@
""" """
PostgreSQL-Integration: Roundtrip _replace_unit_sections ↔ _fetch_sections. PostgreSQL-Integration: Roundtrip _replace_unit_sections ↔ _fetch_sections.
Aktivierung (lokal, analog zu test_access_layer_integration): Aktivierung:
set TRAINING_PLANNING_INTEGRATION=1 - Lokal: TRAINING_PLANNING_INTEGRATION=1
pytest tests/test_training_planning_sections_integration.py -v -m integration - CI: .gitea/workflows/test.yml setzt die Variable beim pytest-Lauf (deployter Backend-Container + PostgreSQL).
Voraussetzung: migrierte DB, DB_* wie Docker-Compose. Voraussetzung: migrierte DB, DB_* wie Docker-Compose.
""" """