From f9b5ab7789739fd6824c2409bb28dc3e9fbf8def Mon Sep 17 00:00:00 2001 From: lukhipolito-nexxbiz Date: Mon, 29 Sep 2025 19:53:54 +0200 Subject: [PATCH] Update doc/qa/test-guidelines.md Co-authored-by: Sipke Schoorstra --- doc/qa/test-guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/qa/test-guidelines.md b/doc/qa/test-guidelines.md index 449276b4a..831c3f6ba 100644 --- a/doc/qa/test-guidelines.md +++ b/doc/qa/test-guidelines.md @@ -9,7 +9,7 @@ This document describes recommended testing strategies for the Elsa engine. It i 1. **Deterministic tests** — tests should not be flaky and should produce the same results independent of circumstance. 2. **Fast feedback** — unit and integration tests should run quickly to support local workflows and CI. -3. **Minimal reliance on real delays** — avoid `Thread.Sleep` or real clocks except where unavoidable; prefer event-driven assertions. +3. **Minimal reliance on real delays** — avoid `Task.Delay`, `Thread.Sleep` or real clocks except where unavoidable; prefer event-driven assertions. 4. **Environment portability** — tests should run in local dev, Docker or any other container CI environment with minimal changes. 5. **Version alignment** — workflow definition versions and test artifacts must be explicitly linked so tests refer to a specific workflow blueprint version. 6. **Bulk provisioning & isolation** — tests should support bulk import of workflow definitions for large-suite runs and ensure clean, isolated state per test.