.toHaveReceivedCommandWith ignoring DeleteCommand and ScanCommand

[ManuelCodes]

Checklist

• [X] I have read Caveats documentation and didn't find a solution for this problem there.

Bug description

Hey there,

Just wanted to flag an issue I'm encountering while running unit tests for a Lambda function with DynamoDB CRUD. It seems like the tests are skipping DeleteCommand and ScanCommand, while PutCommand, QueryCommand, and TransactWriteItemsCommand work fine.

Here is the output:

In case that it is not a bug. Could someone guide me what I am doing wrong?

Thanks in advance

Reproduction

organizations.test.ts

import 'aws-sdk-client-mock-jest';
import {
    DynamoDBDocumentClient,
   PutCommand,
   QueryCommand,
   DeleteCommand,
   ScanCommand
} from "@aws-sdk/lib-dynamodb";
import { TransactWriteItemsCommand,  } from "@aws-sdk/client-dynamodb";

import { mockClient,  } from 'aws-sdk-client-mock';

const mockDynamoDbDocumentClient = mockClient(DynamoDBDocumentClient);

it("should test deleting an organization", async () => {
        mockEvent.body = JSON.stringify({
            "id": "2",
            "organization_name": "ORG#SOMETHING",
        });
        mockDynamoDbDocumentClient.on(DeleteCommand).resolvesOnce({});
        const response = await organizations.deleteOrganization(mockEvent, mockContext, jest.fn());

        //LINE BELOW NOT WORKING
        expect(mockDynamoDbDocumentClient).toHaveReceivedCommandWith(DeleteCommand, {}); 

        expect(response).toMatchObject({
            statusCode: 200,
            body: JSON.stringify('ORG#SOMETHING has been deleted')
        });
});

organizations.ts

export const deleteOrganization:APIGatewayProxyHandler = async (event: APIGatewayProxyEvent, _context: Context, _cb) => {
    const { id, organization_name } = JSON.parse(event.body!);

    try {
        const params = {
            TableName: TIRESHOP_TABLE_NAME,
            Key: { pk:  id, sk:  organization_name },
            //ConditionExpression: "attribute_exists(pk) and attribute_exists(sk)"
        }
        const command = new DeleteCommand(params);
        await client.send(command);

        return {
            statusCode: 200,
            body: JSON.stringify(`${organization_name} has been deleted`)
        };
    } catch(err) {
        console.log(err);
        return {
            statusCode: 500,
            body: JSON.stringify("unknown error")
        };
    }
};

Environment

• Node version: v20.12.2
• Testing lib and version: "jest": "^29.7.0", "@jest/globals": "^29.7.0", "@types/jest": "^29.5.12",
• Typescript version: "typescript": "^5.4.5"
• AWS SDK v3 Client mock version: "aws-sdk-client-mock-jest": "^4.0.0", "aws-sdk-mock": "^6.0.0",
• AWS JS SDK libs and versions: "@aws-sdk/client-dynamodb": "^3.565.0", "@aws-sdk/lib-dynamodb": "^3.565.0", "@types/aws-lambda": "^8.10.137",

[m-radzikowski]

This works perfectly fine for me:

import {DeleteCommand, DynamoDBDocumentClient} from "@aws-sdk/lib-dynamodb";
import {DynamoDBClient} from "@aws-sdk/client-dynamodb";
import {mockClient} from 'aws-sdk-client-mock';
import 'aws-sdk-client-mock-jest';

const client = DynamoDBDocumentClient.from(new DynamoDBClient());

export const deleteOrganization = async () => {
  try {
    const params = {
      TableName: '',
      Key: {pk: '', sk: 'organization_name'},
    }
    const command = new DeleteCommand(params);
    await client.send(command);

    return {
      statusCode: 200,
      body: JSON.stringify(`ORG#SOMETHING has been deleted`),
    };
  } catch (err) {
    console.log(err);
    return {
      statusCode: 500,
      body: JSON.stringify("unknown error"),
    };
  }
};

const mockDynamoDbDocumentClient = mockClient(DynamoDBDocumentClient);

it("should test deleting an organization", async () => {
  mockDynamoDbDocumentClient.on(DeleteCommand).resolvesOnce({});
  const response = await deleteOrganization();

  expect(mockDynamoDbDocumentClient).toHaveReceivedCommandWith(DeleteCommand, {});

  expect(response).toMatchObject({
    statusCode: 200,
    body: JSON.stringify('ORG#SOMETHING has been deleted'),
  });
});

Tested with both AWS SDK v3.565.0 and v3.588.0 (current latest).

One note - if you don't need any assertions on the command content, you can use toHaveReceivedCommand() instead of toHaveReceivedCommandWith(). But still it works fine with empty object.

If the problem persists, please create a sample repo with reproduction and I'll take a look.