From 0041d13f3c30451e45f6d2cf2dfc99400cc5a332 Mon Sep 17 00:00:00 2001 From: lukhipolito-nexxbiz Date: Mon, 29 Sep 2025 20:08:19 +0200 Subject: [PATCH] Update doc/qa/test-guidelines-collaborators.md Co-authored-by: Sipke Schoorstra --- doc/qa/test-guidelines-collaborators.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/qa/test-guidelines-collaborators.md b/doc/qa/test-guidelines-collaborators.md index 2f451d47a..1a36f0e70 100644 --- a/doc/qa/test-guidelines-collaborators.md +++ b/doc/qa/test-guidelines-collaborators.md @@ -20,7 +20,7 @@ This document describes recommended testing strategies for the Elsa engine. It i ## High‑level testing pyramid for Elsa -- **Unit tests**: Activity logic, expression evaluators, small helpers. In‑process, mocking storage and scheduler. Fast and numerous. +- **Unit tests**: Activity logic, expression evaluators, services, providers, small helpers. In‑process, mocking storage and scheduler. Fast and numerous. - Use [xUnit / NUnit / MSTest] with [Moq / NSubstitute] for mocking. Test activities and small components in isolation. Use in‑memory stores. - **Component/integration tests**: Core engine components (WorkflowInvoker, Bookmark handling, persistence adapters) with in‑memory or ephemeral DB. Use fake clock and fake scheduler. Run in CI and locally. - Use `TestHostFactory` to create test hosts with DI overrides. Use code-first or serialized workflow definitions depending on the amount and scope. Also, possible to use external tooling like JTest.