PYS/IPSExtractor
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Update docker-compose configuration to use environment variables for sensitive data, enhance testing documentation with new LaTeX files for capacity planning, and refine README for clarity on compilation and testing processes.

Browse Source
This commit is contained in:
erik
2026-07-17 08:32:00 -05:00
parent e47ef4f8c6
commit dc3fcc2280
89 changed files with 5331 additions and 1210 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plan_pruebas/sections/04_unitarias.tex
+17 -14
View File
@@ -1,33 +1,36 @@
\chapter{Pruebas unitarias}
\label{ch:unitarias}
Las unitarias cubren \textbf{regresiones de dominio} sin levantar el stack completo.
Un fallo aqu\'i suele ser m\'as barato de corregir que un fallo E2E.
\section{Gateway}
\begin{longtable}{@{}p{2.4cm}p{4.2cm}p{5.5cm}@{}}
\begin{longtable}{@{}p{2.2cm}p{3.5cm}p{4.0cm}p{3.0cm}@{}}
\caption{Unitarias gateway.}\\
\toprule
\textbf{ID} & \textbf{Caso} & \textbf{Criterio de \'exito} \\
\textbf{ID} & \textbf{Caso} & \textbf{Criterio de \'exito} & \textbf{Riesgo} \\
\midrule
\endhead
UT-GW-01 & Clasificaci\'on path upload vs JSON & Timeouts 600\,s vs 30\,s correctos \\
UT-GW-02 & Health live sin upstream & Respuesta inmediata \texttt{ok} \\
UT-GW-03 & Health agregado degradado & Si extraction/cleaning fallan $\rightarrow$ \texttt{degraded} \\
UT-GW-01 & Path upload vs JSON & Timeouts 600\,s vs 30\,s & Uploads cortados \\
UT-GW-02 & Health live sin upstream & \texttt{ok} inmediato & Orquestaci\'on ciega \\
UT-GW-03 & Health agregado degradado & Upstream down $\rightarrow$ \texttt{degraded} & Falsos ``todo ok'' \\
\bottomrule
\end{longtable}
\section{Bot-descarga API (\texttt{JobStore})}
Cobertura existente en \texttt{test\_store.py}; ampliar con:
\begin{longtable}{@{}p{2.6cm}p{4.0cm}p{5.5cm}@{}}
Cobertura en \texttt{test\_store.py}; ampliar con:
\begin{longtable}{@{}p{2.4cm}p{3.4cm}p{3.8cm}p{3.0cm}@{}}
\caption{Unitarias bot-descarga API.}\\
\toprule
\textbf{ID} & \textbf{Caso} & \textbf{Criterio de \'exito} \\
\textbf{ID} & \textbf{Caso} & \textbf{Criterio de \'exito} & \textbf{Riesgo} \\
\midrule
\endhead
UT-BOT-01 & Register + heartbeat & Worker online; offline tras $>$45\,s \\
UT-BOT-02 & Claim at\'omico & Un solo worker obtiene el job \\
UT-BOT-03 & Cancel pending & Estado \texttt{cancelled} inmediato \\
UT-BOT-04 & Cancel running & \texttt{cancel\_requested=true} \\
UT-BOT-05 & Auth Bearer & Token inv\'alido $\rightarrow$ 401 \\
UT-BOT-06 & Keys MinIO & Prefijos uploads/downloads correctos \\
UT-BOT-01 & Register + heartbeat & Online; offline $>$45\,s & Jobs a PCs muertos \\
UT-BOT-02 & Claim at\'omico & Un solo worker & Doble descarga \\
UT-BOT-03 & Cancel pending & \texttt{cancelled} & Jobs fantasma \\
UT-BOT-04 & Cancel running & \texttt{cancel\_requested} & Selenium sin freno \\
UT-BOT-05 & Auth Bearer & 401 si inv\'alido & Acceso indebido \\
UT-BOT-06 & Keys MinIO & Prefijos correctos & PDFs perdidos \\
\bottomrule
\end{longtable}