Struct aws_smithy_mocks_experimental::RuleBuilder

pub struct RuleBuilder<I, O, E> { /* private fields */ }

Implementations

impl<I, O, E> RuleBuilder<I, O, E>

where I: Send + Sync + Debug + 'static, O: Send + Sync + Debug + 'static, E: Send + Sync + Debug + Error + 'static,

pub fn new<F, R>( _input_hint: impl Fn() -> I, _output_hint: impl Fn() -> F, ) -> Self

where F: Future<Output = Result<O, SdkError<E, R>>>,

Creates a new RuleBuilder. This is normally constructed with the mock! macro

pub fn match_requests( self, filter: impl Fn(&I) -> bool + Send + Sync + 'static, ) -> Self

Add an additional filter to constrain which inputs match this rule.

For examples, see the examples directory of this repository.

pub fn then_http_response( self, response: impl Fn() -> HttpResponse + Send + Sync + 'static, ) -> Rule

If the rule matches, then return a specific HTTP response.

This is the recommended way of testing error behavior.

pub fn then_output(self, output: impl Fn() -> O + Send + Sync + 'static) -> Rule

If a rule matches, then return a specific output

pub fn then_error(self, output: impl Fn() -> E + Send + Sync + 'static) -> Rule

If a rule matches, then return a specific error

Although this basically works, using then_http_response is strongly recommended to create a higher fidelity mock. Error handling is quite complex in practice and returning errors directly often will not perfectly capture the way the error is actually returned to the SDK.