loadtester

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

type DoRetryChecker interface {
	DoRetryer
	RetryChecker
}

type DoRetryer interface {
	Doer
	Retryer
}

type Doer interface {
	Do(ctx context.Context, workerID int) error
}

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

type LoadtestOption func(*loadtestConfig)

type RetryChecker interface {
	CanRetry(ctx context.Context, workerID int, prevErr error) bool
}

type Retryer interface {
	Retry(ctx context.Context, workerID int, prevErr error) error
}

type StructuredLogger interface {
	Debug(msg string, keysAndValues ...any)
	DebugContext(ctx context.Context, msg string, keysAndValues ...any)
	Warn(msg string, keysAndValues ...any)
	WarnContext(ctx context.Context, msg string, keysAndValues ...any)
	Error(msg string, keysAndValues ...any)
	ErrorContext(ctx context.Context, msg string, keysAndValues ...any)
	Info(msg string, keysAndValues ...any)
	InfoContext(ctx context.Context, msg string, keysAndValues ...any)
}

type TaskReader interface {
	// ReadTasks fills the provided slice up to slice length starting at index 0 and returns how many records have been inserted
	//
	// Failing to fill the whole slice will signal the end of the loadtest.
	//
	// Note in general you should not use this behavior to signal loadtests to stop
	// if your loadtest needs to be time-bound. For that case you should signal a stop
	// via the context. This stop on failure to fill behavior only exists for cases
	// where the author wants to exhaustively run a set of tasks and not bound the
	// loadtest to a timespan but rather completeness of the tasks space.
	//
	// Note that if you have only partially filled the slice, those filled task slots
	// will still be run before termination of the loadtest.
	//
	// It is important to remember that if your loadtest loops around and you keep a large slice of
	// tasks in memory just to place small chunks of that list into the passed in slice of this function
	// that you could have a task executed by two separate goroutines at the same time under the right circumstances.
	// Therefore, it's really important that the tasks either be stateless or concrete copies of the original task object are
	// created when saved to the passed in slice of this function.
	ReadTasks([]Doer) int
}