test(server-nestjs): audit de parité de migration + parité unit/e2e vault-zone - #2578
Draft
shikanime wants to merge 3 commits into
Draft
test(server-nestjs): audit de parité de migration + parité unit/e2e vault-zone#2578shikanime wants to merge 3 commits into
shikanime wants to merge 3 commits into
Conversation
…e parity Signed-off-by: William Phetsinorath <william.phetsinorath-open@interieur.gouv.fr> Change-Id: Iecda25d80f34897d6c421615f94040536a6a6964
Open
10 tasks
Co-authored-by: Automata <automata@shikanime.studio>
Member
Author
|
Ajout d'une section « Cahier traceability » dans TESTING-CAMPAIGN.md : mapping des scénarios du cahier fonctionnel vers les specs automatisées livrées (PROJ-001/003/010, PLUG-004, ZONE-001, GIT-006, ADMIN-003, TODO-003). |
…x imports Signed-off-by: William Phetsinorath <william.phetsinorath-open@interieur.gouv.fr> Change-Id: Idaac595c61d7b22834e97676e8ac565f6a6a6964
|
4 New Issues
0 Fixed Issues
0 Accepted Issues
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issues liées
#2574 #2575
Quel est le comportement actuel ?
La migration
apps/server→apps/server-nestjsn'a aucun artefact de suivi de parité : les écarts d'événements (hook.<entity>.<verb>legacy vs émetteurs/listeners nestjs) ne sont documentés nulle part et aucune spec ne verrouille le comportement actuel.Quel est le nouveau comportement ?
documentation/MIGRATION-PARITY-MATRIX.md: inventaire complet des hooks legacy (43× project.upsert, 8× adminRole, 5× zone…) croisé avec les émetteurs/listeners nestjs.documentation/TESTING-CAMPAIGN.md: décomposition de la campagne de tests.app-events.service.spec.ts: +4 tests — surface d'émission verrouillée + garde négative « pas d'emitZoneEvent » tant que la route zone est côté legacy.vault.service.spec.ts: +4 tests — contrat externeupsertZone/deleteZone(mount KV, policy ro, approle, fallback tune-400, tolérance NotFound).test/vault.e2e-spec.ts: cas zone lifecycle (gatedE2E, non exécuté ici — hôtes intégration inaccessibles depuis ce poste).Suite unitaire : 586 passed / 61 skipped (zéro régression, baseline 578).
Cette PR introduit-elle un breaking change ?
Non.
Autres informations
Tests uniquement (specs + documentation). Les blocants cutover sont tracés dans #2575/#2576/#2577.