From 96f2d1d23a45b0ceb3ba01a260bb5d1261fc5a5e Mon Sep 17 00:00:00 2001 From: "lucas.hipolito" Date: Fri, 26 Sep 2025 15:17:03 +0200 Subject: [PATCH] Removing bogus information from test-guidelines.md --- doc/qa/test-guidelines.md | 25 ------------------------- 1 file changed, 25 deletions(-) diff --git a/doc/qa/test-guidelines.md b/doc/qa/test-guidelines.md index 4927ddeea..449276b4a 100644 --- a/doc/qa/test-guidelines.md +++ b/doc/qa/test-guidelines.md @@ -1,28 +1,3 @@ -# Test Guidelines - -## dump - -Consider the following constraints to have the best possible way of testing of the elsa engine - -- Not be affected by execution times -- not having to depend on delays unless there is no other way -- how do we get the workflow definitions in the engine - - is the test responsible for publish - - can it be in bulk by an import - - can it work with docker, env, k8s cluster deployments - - how can we manage the tests version with the workflow definition version? -- what are steps that we need, the templates to not have repetitive implementations -- is the journal and activity execution endpoints the best to do the asserts upon. -- are there alternatives like querying the db -..... -- is execute the best to test the activities or a workflow with and http endpoint -- how to test failures , like the fail activity, no workflow instance returned no way to find the instance - - or by using a correlation id - - how to avoid get latest instance of a definition etc. - -the goal is to have a testing environment that is consistent in the execution. - ---- # Elsa Core — Test Strategy Guidelines **Purpose:**