Skip to content

Conversation

@bbortt
Copy link
Collaborator

@bbortt bbortt commented May 26, 2025

tests being introduced first, for #328. these will act as regression tests.

@bbortt bbortt self-assigned this May 26, 2025
@bbortt bbortt mentioned this pull request May 26, 2025
@bbortt
Copy link
Collaborator Author

bbortt commented May 26, 2025

with this tests the ScenarioEndpoint has a coverage of 100% linse | 100% methods | 50% branches

@bbortt bbortt force-pushed the feat/concurrency-issue-tests branch from f913827 to f5d8775 Compare May 26, 2025 11:57
@bbortt bbortt requested a review from tschlat May 26, 2025 11:57
@bbortt bbortt added READY Type: Maintenance Prio: High java Pull requests that update Java code labels May 26, 2025
bbortt added 2 commits July 2, 2025 15:57
it may occur that two scenarios run at the same time (with only a millisecond off).
if that happens, the `Stack` implementation in `ScenarioEndpoint` does not respect FIFO order.
the second message receives the output of the first.
this commit introduces a nice link between a scenario and its messages.
an object is being attached to the `TestContext` which is unique per scenario execution.
both the received `Message` as well as the response `Future` are contained in it.
@bbortt bbortt changed the title introduce more tests for scenario endpoint Draft: refactored scenario endpoint for high concurrency Jul 2, 2025
@bbortt bbortt added IN PROGRESS and removed READY labels Jul 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants