Documentation

Overview

Package sagemakerfeaturestoreruntimeiface provides an interface to enable mocking the Amazon SageMaker Feature Store Runtime service client for testing your code.

It is important to note that this interface will have breaking changes when the service model is updated and adds new API operations, paginators, and waiters.

Index

Constants

This section is empty.

Variables

This section is empty.

Functions

This section is empty.

Types

type SageMakerFeatureStoreRuntimeAPI

SageMakerFeatureStoreRuntimeAPI provides an interface to enable mocking the sagemakerfeaturestoreruntime.SageMakerFeatureStoreRuntime service client's API operation, paginators, and waiters. This make unit testing your code that calls out to the SDK's service client's calls easier.

The best way to use this interface is so the SDK's service client's calls can be stubbed out for unit testing your code with the SDK without needing to inject custom request handlers into the SDK's request pipeline.

// myFunc uses an SDK service client to make a request to
// Amazon SageMaker Feature Store Runtime.
func myFunc(svc sagemakerfeaturestoreruntimeiface.SageMakerFeatureStoreRuntimeAPI) bool {
    // Make svc.DeleteRecord request
}

func main() {
    sess := session.New()
    svc := sagemakerfeaturestoreruntime.New(sess)

    myFunc(svc)
}

In your _test.go file:

// Define a mock struct to be used in your unit tests of myFunc.
type mockSageMakerFeatureStoreRuntimeClient struct {
    sagemakerfeaturestoreruntimeiface.SageMakerFeatureStoreRuntimeAPI
}
func (m *mockSageMakerFeatureStoreRuntimeClient) DeleteRecord(input *sagemakerfeaturestoreruntime.DeleteRecordInput) (*sagemakerfeaturestoreruntime.DeleteRecordOutput, error) {
    // mock response/functionality
}

func TestMyFunc(t *testing.T) {
    // Setup Test
    mockSvc := &mockSageMakerFeatureStoreRuntimeClient{}

    myfunc(mockSvc)

    // Verify myFunc's functionality
}

It is important to note that this interface will have breaking changes when the service model is updated and adds new API operations, paginators, and waiters. Its suggested to use the pattern above for testing, or using tooling to generate mocks to satisfy the interfaces.

Source Files