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
{{ message }}
This repository has been archived by the owner on Jun 12, 2021. It is now read-only.
Adam Ralph edited this page Feb 23, 2018
·
2 revisions
This problem occurs when a step contains an expression which returns a Task which will never be completed.
For example, an expression which assigns a Task variable will return that Task:
"Given a task".x(()=>task=newTask(()=>{}));
When the step is executed, xBehave.net will await the Task before executing the next step. Because the Task never completes, the step will never complete.
The workaround is to use a block instead of an expression: