test: automatizar 6 tests pendientes del test plan#11
Merged
Conversation
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.
What
Automatiza los 6 tests marcados como
Pendingen el test plan, llevando la cobertura de Iteración X de 58.8% a 100%.Why
La entrega requiere evidencia de tests automatizados para todos los casos del test plan. Los 6 casos cubrían features reales del sistema que no tenían test unitario.
Changes
TaskServiceTest.java— añadidos tests Add PROJECT_CONTEXT.md with explicit OCI infrastructure and database context #6 (createTask happy path con todos los campos) y Exportación CSV no respeta filtros activos del dashboard #7 (updateTask cambia título, prioridad y sprint)TaskRequestValidationTest.java(nuevo) — tests feat(validation): limites de inputs, mensajes de error y manejo de caracteres inusuales #10 (título vacío falla validación Bean Validation) y ci(cd): agregar workflow de rollback al deploy anterior #12 (título solo con emojis pasa validación)NotificationServiceTest.java(nuevo) — test Switch NLU model from Sonnet to Haiku for cost efficiency #16 (TASK_BLOCKED envía mensaje Telegram al manager víaTelegramClient)TaskStatusHandlerTest.java(nuevo) — test feat: Dashboard KPI — Avg/Median por dev y filtros por sprint/dev #17 (comando/task_statuscon status inválido devuelve error amigable con lista de valores válidos)Todos los tests siguen el patrón existente: JUnit 5 + Mockito puro, sin Spring context, sin base de datos.
Suite completa: 39/39 tests — BUILD SUCCESS