infrastructure/plunk
2
0
Fork 0
Code Pull Requests Activity

tests: prevent race condition by inserting RUNNING execution directly

Browse Source
This commit is contained in:
Dries Augustyns
2026-05-27 18:08:13 +02:00
parent 480f0c1034
commit 58be4abc31
1 changed files with 12 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/api/src/services/__tests__/WorkflowService.test.ts
+12 -2
View File
@@ -758,8 +758,18 @@ describe('WorkflowService', () => {
}); });
const contact = await factories.createContact({projectId}); const contact = await factories.createContact({projectId});
// Start first execution (still running) // Insert a RUNNING execution directly to avoid racing with the background
await WorkflowService.startExecution(projectId, workflow.id, contact.id); // step processor that startExecution kicks off (a trigger-only workflow can
// transition to COMPLETED before the second call observes it as RUNNING).
const triggerStep = workflow.steps.find(step => step.type === WorkflowStepType.TRIGGER);
await prisma.workflowExecution.create({
data: {
workflowId: workflow.id,
contactId: contact.id,
status: WorkflowExecutionStatus.RUNNING,
currentStepId: triggerStep?.id,
},
});
// Second execution should fail (first still running) // Second execution should fail (first still running)
await expect(WorkflowService.startExecution(projectId, workflow.id, contact.id)).rejects.toThrow( await expect(WorkflowService.startExecution(projectId, workflow.id, contact.id)).rejects.toThrow(