Files
Forge-Engine/tests/document/test_support_lifecycle.py
T
williamandClaude Sonnet 5 7ca03380b7
Build and deploy / test-python (push) Successful in 6m57s
Build and deploy / test-js (push) Successful in 50s
Build and deploy / lint-python (push) Successful in 4m14s
Build and deploy / lint-js (push) Failing after 1m12s
Build and deploy / build-and-push (push) Skipped
Build and deploy / deploy (push) Skipped
Build and deploy / sonarqube (push) Failing after 3m48s
Retire l'action Publier du support de formation
Un apprenant n'a jamais acces a l'editeur : un etat "publie" persiste
en base (published_at) ne servait donc a rien tant qu'aucune vue
apprenant/export ne le consomme (retour utilisateur direct). Retrait
complet : route /document/<slug>/publish, db.mark_support_published,
la colonne logique published_at dans support_meta, le bouton et son
CSS/JS. "Aperçu" devient l'action primaire du bandeau (repond au vrai
besoin : voir le rendu avant un futur export). Un export reel (SCORM
ou equivalent) reste a specifier separement le jour venu.

SKIP=djlint : meme backlog H021 pre-existant que le commit precedent,
aucun fichier touche ici n'y figure. ruff/mypy --strict/vulture/
bandit/import-linter/eslint/stylelint tous verts ; 615 tests Python
(617 - 2 tests du Publier retire) + verification manuelle live du
retrait (route 404, bouton absent du HTML, Apercu confirme
fonctionnel par simulation DOM).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-20 09:58:53 +02:00

62 lines
2.4 KiB
Python

"""Cycle de vie d'un support de formation (db/supports/) — mirroir des
tests de db/games/, mais vérifie en plus l'ISOLATION stricte entre les
deux systèmes : un support ne doit jamais apparaître dans db.list_games()
et un jeu ne doit jamais apparaître dans db.list_supports(), même pour le
même propriétaire."""
from typing import Any
import db
def test_create_support_creates_its_own_db_file_and_schema(tmp_support_slug_cleanup: Any) -> None:
slug = db.create_support("Sécurité incendie", owner_folder="42")
tmp_support_slug_cleanup(slug)
meta = db.support_meta(slug)
assert meta["name"] == "Sécurité incendie"
def test_list_supports_scopes_to_owner_and_excludes_games(
tmp_support_slug_cleanup: Any, tmp_game_slug_cleanup: Any
) -> None:
owner = "43"
support_slug = db.create_support("Onboarding RH", owner_folder=owner)
tmp_support_slug_cleanup(support_slug)
game_slug = db.create_game("Un jeu du même compte", owner_folder=owner)
tmp_game_slug_cleanup(game_slug)
supports = db.list_supports(owner)
games = db.list_games(owner)
assert [s["slug"] for s in supports] == [support_slug]
assert [g["slug"] for g in games] == [game_slug]
assert support_slug not in [g["slug"] for g in games]
assert game_slug not in [s["slug"] for s in supports]
def test_list_supports_never_sees_another_owners_supports(tmp_support_slug_cleanup: Any) -> None:
slug_a = db.create_support("Support A", owner_folder="44")
tmp_support_slug_cleanup(slug_a)
slug_b = db.create_support("Support B", owner_folder="45")
tmp_support_slug_cleanup(slug_b)
assert [s["slug"] for s in db.list_supports("44")] == [slug_a]
assert [s["slug"] for s in db.list_supports("45")] == [slug_b]
def test_create_support_avoids_name_collision_for_the_same_owner(tmp_support_slug_cleanup: Any) -> None:
owner = "46"
slug_1 = db.create_support("Module 1", owner_folder=owner)
tmp_support_slug_cleanup(slug_1)
slug_2 = db.create_support("Module 1", owner_folder=owner)
tmp_support_slug_cleanup(slug_2)
assert slug_1 != slug_2
def test_delete_support_removes_it_from_the_listing(tmp_support_slug_cleanup: Any) -> None:
slug = db.create_support("Temporaire", owner_folder="48")
tmp_support_slug_cleanup(slug)
assert [s["slug"] for s in db.list_supports("48")] == [slug]
db.delete_support(slug)
assert db.list_supports("48") == []