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
On our test suite, I've noticed that Oban.Pro.Testing.run_workflow/2 runs jobs that are scheduled during the workflow execution but don't belong to the workflow.
I would expect that run_workflow/2 would run only the jobs that share the workflow_id, not drain all the scheduled jobs. If that is intended, I suggest adding a note to the function documentation.
The text was updated successfully, but these errors were encountered:
thiagopromano
changed the title
Oban.Pro.Testing.run_worflow/2 drain jobs not related to workflowOban.Pro.Testing.run_workflow/2 drain jobs not related to workflow
Dec 18, 2024
I would expect that run_workflow/2 would run only the jobs that share the workflow_id, not drain all the scheduled jobs. If that is intended, I suggest adding a note to the function documentation.
That's a perfectly normal expectation and the quirk bites people every once in a while. Working on a fix rather than a caveat in the docs.
Environment
1.5.0-rc.6
Current Behavior
On our test suite, I've noticed that
Oban.Pro.Testing.run_workflow/2
runs jobs that are scheduled during the workflow execution but don't belong to the workflow.I would expect that
run_workflow/2
would run only the jobs that share theworkflow_id
, not drain all the scheduled jobs. If that is intended, I suggest adding a note to the function documentation.The text was updated successfully, but these errors were encountered: