Feature Request: .toHaveProperties(arguments: string[]) matcher

What is the current behavior? Currently Jest offers .toHaveProperty to check for a specific property inside an object but I couldn’t see an easy way of checking for multiples properties. I am aware that Jest offers expect.extend() to make possible for us to customize a matcher, but checking for more than one property seems quite usual to me. Wouldn’t it be interesting to have a .toHaveProperties(args) matcher that receives an array of strings to check?

A fast and naive prototype of what I am proposing using expect.extend:

const extend = {
  toHaveProperties(received, args) {
    const receivedProperties = Object.getOwnPropertyNames(received);
    const pass = !args.some(val => receivedProperties.indexOf(val) === -1);
    if (pass) {
      return {
        message: () => `expected ${received} not to have properties of ${args}`,
        pass: true,
      };
    } else {
      return {
        message: () => `expected ${received} to have properties of ${args}`,
        pass: false,
      };
    }
  },
};
expect.extend(extend)
``

[mattphillips]

@elad-yosifon have you checked out jest-extended? It has support for toContainKeys which is the same API to your example toHaveKeys.

@WederPachecoSilva jest-extended also has APIs for checking entries (key/value pairs) in an object see toContainEntries

[elad-yosifon]

@SimenB @WederPachecoSilva … maybe changing the function to

expect().toHaveKeys(...keys :string[])

will be a better idea?