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

Flow Join integration tests - Reducing unnecessary logic

Browse source
This commit is contained in:
lucas.hipolito 2025-11-05 08:59:28 +01:00
parent 66b94edd61
commit 321c4cebc1
1 changed files with 11 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
test/integration/Elsa.Activities.IntegrationTests/Branching/FlowJoinTests.cs
View file

@ -60,21 +60,17 @@ public class FlowJoinTests : IDisposable
// Assert
Assert.Contains("Start", _output.Lines);
// Document expected behavior for different combinations
if (useTokenFlow)
{
// In token flow mode, both WaitAny and WaitAll should act as no-ops
// The flowchart should execute normally: Start -> FlowJoin -> AfterJoin
Assert.Contains("AfterJoin", _output.Lines);
}
else
{
// In counter flow mode:
// - WaitAny should allow continuation after first inbound connection
// - WaitAll should wait for all inbound connections (in this case just one)
// Since there's only one inbound connection, both should behave similarly
Assert.Contains("AfterJoin", _output.Lines);
}
// In token flow mode, both WaitAny and WaitAll should act as no-ops
// The flowchart should execute normally: Start -> FlowJoin -> AfterJoin
// In counter flow mode:
// - WaitAny should allow continuation after first inbound connection
// - WaitAll should wait for all inbound connections (in this case just one)
// Since there's only one inbound connection, both should behave similarly
Assert.Contains("AfterJoin", _output.Lines);
}
[Theory]