From c9be7f0d13a88553b154b087073716870578ef97 Mon Sep 17 00:00:00 2001 From: lukhipolito-nexxbiz Date: Thu, 9 Oct 2025 14:49:00 +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 618e39ee4..5d75a5ec6 100644 --- a/doc/qa/test-guidelines.md +++ b/doc/qa/test-guidelines.md @@ -11,7 +11,7 @@ The philosophy of testing in Elsa can be summarized as: ***Whenever a test fails, it should provide a clear direction towards the cause of the problem.*** -Tests should be fast, deterministic, and precise: they should pinpoint the failing subsystem (activity, invoker, persistence, scheduler) with minimal noise. +Tests should be fast, deterministic, and precise: they should pinpoint the failing subsystem (activity, invoker, persistence, scheduler, etc.) with minimal noise. For contributors, tests are the first line of code review: they must document intended behaviour and prevent regressions.