From e0f353fb3508407d43817e52cac7399088a97402 Mon Sep 17 00:00:00 2001 From: lukhipolito-nexxbiz Date: Fri, 3 Oct 2025 12:43:57 +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 c31effe1a..4ec82c271 100644 --- a/doc/qa/test-guidelines-collaborators.md +++ b/doc/qa/test-guidelines-collaborators.md @@ -41,7 +41,7 @@ This means that if it does not point directly to the source of the issue, it sho - Place workflow definitions in a `Workflows/` folder located in the root of the test (see [`MigrationTests`](../../test/integration/Elsa.Alterations.IntegrationTests/MigrationTests.cs)). - Use serialized workflow or code-first definitions depending on the amount and scope. - Also, possible to use external tooling like [JTest](https://github.com/nexxbiz/jtest). -- **Component tests**: Larger workflows with multiple activities, versioning, and persistence. +- **Component tests**: Exercises multiple components end to end, e.g. all the way from a REST API endpoint down to the persistence layer, touching everything in between. - Use real DB (local ephemeral DB). Run in CI and locally. - Use real components (e.g. [`IWorkflowRuntime`](../../src/modules/Elsa.Workflows.Runtime/Contracts/IWorkflowRuntime.cs), see [`ExecuteWorkflowsTests`](../../test/component/Elsa.Workflows.ComponentTests/Scenarios/ExecuteWorkflows/ExecuteWorkflowsTests.cs)). - Use [`AppComponentTest`](../../test/component/Elsa.Workflows.ComponentTests/Helpers/Abstractions/AppComponentTest.cs) with real DB provider.