nobuffer

type NoBuffer ¶

type NoBuffer struct {
	// contains filtered or unexported fields
}

NoBuffer runs the loadbalance/earlyresult fault sequence against a worker that does not buffer an early resolution. Like the Python, Java and JavaScript SDKs, it replays the events in order and ignores a resolution with no pending activity, timer or child workflow, and it gives every new scheduling a new TaskExecutionId. The workflow runs step0, then a middle step, then step2; the turn that schedules the middle step fails its save after the step was started, so its resolution reaches the inbox before its scheduling is saved. The workflow must still complete.

func New(t *testing.T, opts Options) *NoBuffer

func (n *NoBuffer) Cleanup(t *testing.T)

func (n *NoBuffer) Execute(t *testing.T, ctx context.Context)

func (n *NoBuffer) Run(t *testing.T, ctx context.Context)

type Options ¶

type Options struct {
	// ID is the workflow instance ID; the child workflow is ID + "-child".
	ID     string
	Middle Step
	// HoldChild holds the child's terminal commit, and with it the child's
	// turn lock, until the parent's retried turn is blocked re-creating the
	// child.
	HoldChild bool
}

type Step ¶

type Step int

Step is the kind of the workflow's middle step.

const (
	StepActivity Step = iota
	StepTimer
	StepChild
)