SemianiakaVY/elsa-core
1
0
Fork 0
Code Issues Pull requests Actions 1 Packages Projects Releases Wiki Activity

Removing bogus information from test-guidelines.md

Browse source
This commit is contained in:
lucas.hipolito 2025-09-26 15:17:03 +02:00
parent 57459da885
commit 96f2d1d23a
1 changed files with 0 additions and 25 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
doc/qa/test-guidelines.md
View file

@ -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:**