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
// Workflows always run to completion, or time-out
363
+
require.True(t, tester.WorkflowFinished())
364
+
365
+
varwrint
366
+
varwerrstring
367
+
tester.WorkflowResult(&wr, &werr)
368
+
require.Equal(t, 59, wr)
369
+
require.Empty(t, werr)
370
+
371
+
// Ensure any expectations set for activity or sub-workflow mocks were met
372
+
tester.AssertExpectations(t)
373
+
}
374
+
```
375
+
376
+
- Timers are automatically fired by advancing a mock workflow clock that is used for testing workflows
377
+
- You can register callbacks to fire at specific times (in mock-clock time). Callbacks can send signals, cancel workflows etc.
378
+
347
379
## Versioning
348
380
349
381
For now, I've intentionally left our versioning. Cadence, Temporal, and DTFx all support the concept of versions for workflows as well as activities. This is mostly required when you make changes to workflows and need to keep backwards compatibility with workflows that are being executed at the time of the upgrade.
0 commit comments