Verificación del verificador #1
Labels
No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Pilot
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Due date
No due date set.
Dependencies
No dependencies set.
Reference: trustchain-oc1-orchestral/ssikit_trustchain#1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hemos de ver cómo integrar el portal verificador en el testing, tanto via frontend (UI), como backend.
Para hablar y concretar.
Hay diferentes tests
forman parte de CI pipeline
b004e3ee27/.gitea/workflows/ci-pipeline.yaml (L68)
b004e3ee27/.gitea/workflows/ci-pipeline.yaml (L109)
b004e3ee27/.gitea/workflows/ci-pipeline.yaml (L151)
tests de momento manuales
muevo esta tarea a verificación, valorar si con https://gitea.pangea.org/trustchain-oc1-orchestral/ssikit_trustchain/issues/1#issuecomment-1445 ya tenemos suficiente o nos estamos dejando de testear algo importante, especificar qué y con detalle
Prueba completa con entrega de mensaje al verificador (email).