Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Allow mocking child workflows like activites #524

Open
KorDum opened this issue Nov 7, 2024 · 0 comments
Open

[Feature Request] Allow mocking child workflows like activites #524

KorDum opened this issue Nov 7, 2024 · 0 comments
Labels
enhancement Feature New feature or request Tests Update tests or testing tools

Comments

@KorDum
Copy link

KorDum commented Nov 7, 2024

Is your feature request related to a problem? Please describe.

In a situation where one workflow starts a child workflow, there is no way to replace the child workflow with a stub. Or I don't understand how to do it - there is no word about it in the documentation.

I found some strange behavior that led me to these thoughts.
Let's imagine that we have two workflows:

  1. Workflow A
  2. Workflow B, which is run via asyncDetached in Workflow A. Workflow B has a timer for 30 minutes

This tricky setup of two workflows allows to detect a bug (as I think). If we run an integration test on Workflow A where only the activity are replaced with stubs, then run an integration test on Workflow B, the timer waits an honest 30 minutes.

If we run only the test on Workflow B, the timer will run instantly without any waiting.

Describe the solution you'd like

It seems that if you replace Workflow B in the test for Workflow A with a stub, this strange problem goes away.

@roxblnfk roxblnfk added Tests Update tests or testing tools Feature New feature or request labels Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature New feature or request Tests Update tests or testing tools
Projects
None yet
Development

No branches or pull requests

2 participants