You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of our Integration Test suite, there are a lot of tests, and all of them create 1 workflow or more, runs assertions, and marks the test as passed.
Test1 starts the worker and service
Kicks off 2 workflows
2nd doesn't start, cool, move on, that's what we wanted to test
close the worker and service
workflow might still be running, waiting for workers
Test2 starts the worker and service
Runs its workflow
Waits for a while (for the timeout to happen) inTest2 workflow
The running workflow from Test1 finds a worker running, and kicks off requests
test fails because it didn't expect the call from the other workflow
The solution here is to ensure that each Integration Test closes the workflows it created before finishing.
The text was updated successfully, but these errors were encountered:
As part of our Integration Test suite, there are a lot of tests, and all of them create 1 workflow or more, runs assertions, and marks the test as passed.
This has lead to situations where workflows are left open, and then they are trying to interact with another tests worker, which fails the tests. E.g.:
Test1
starts the worker and serviceKicks off 2 workflows
2nd doesn't start, cool, move on, that's what we wanted to test
close the worker and service
workflow might still be running, waiting for workers
Test2
starts the worker and serviceRuns its workflow
Waits for a while (for the timeout to happen) in
Test2
workflowThe running workflow from
Test1
finds a worker running, and kicks off requeststest fails because it didn't expect the call from the other workflow
The solution here is to ensure that each Integration Test closes the workflows it created before finishing.
The text was updated successfully, but these errors were encountered: