selector on key-prop doesnt return any matches.

[krsmedlund]

Either its a bug or it probably should be documented that this prop does not work

let wrapper = shallow(<div><div key="foo" /></div>)
expect(wrapper.contains(<div key="foo" />)).toEqual(true) // No error
expect(wrapper.find('[key="foo"]').length).toEqual(1) // Error: Expected 0 to equal 1
expect(wrapper.find({key:"foo"}).length).toEqual(1) // Error: Expected 0 to equal 1

[ljharb]

This is intentional. "key" is not a real prop, it's a magic thing React uses to identify array items.

In other words, you need to use a different name than "key".

[aweary]

You can read more about key here: https://facebook.github.io/react/docs/lists-and-keys.html#keys

[untsamphan]

It would be nice if this is mentioned in the doc ( http://airbnb.io/enzyme/docs/api/selector.html ).

[ljharb]

enzyme docs naturally assume that you've previously read the React docs; but sure, a PR to make our docs link to the React docs on "key" and "ref" would be great.

[melinath]

As someone who has read the React docs and worked with it extensively, I'd like to say:

1. It is not obvious to me from the selector docs that key would not be usable in a selector, since key isn't mentioned and since enzyme is specifically designed to work with React.
2. It would make a lot of sense to me (and apparently to other people) if enzyme did work with key, since again enzyme is specifically designed to work with react, but I understand your decision & just wish it were better documented.
3. The condescending comment about the React docs was really unnecessary and dismissive.

[WalterWeidner]

You can do this instead:

wrapper.findWhere(node => node.key() === 'foo');

[lobsterkatie]

I'd like to second point 2) of @melinath 's post above - key is exactly the kind of thing which we should be able to select on, since the use case for wanting to search on it (you have multiple instances of the same component) is precisely the same case in which react forces you to have it (and forces it to be unique, making it a good selector).

It would great if enzyme would reconsider this decision.

[ljharb]

@lobsterkatie per #645 (comment), you can already do this - just using findWhere, not find.

[WalterWeidner]

One issue I ran into using the findWhere() approach is that you will get errors when the current node isn't an element. I just wrote a function to check for that though.

[ljharb]

@WalterWeidner n && n.whatever should handle that?

[Wgil]

What about testing the key prop to match a specific value using something like:

expect(
  wrapper.contains([<A key={id} />, <B key={id} />])
).toBeTruthy()

You could simply pass the same id to all the Nodes and it is going to work when it should not.

[kepope3]

Add an id (or some other identifier) to your div, or even better create a component

let wrapper = shallow(
      <div>
        <div id="fooId" key="foo" />
      </div>
    );

Then use standard find to get the key function instead of findWhere

expect(wrapper.find("#fooId").key()).toBe("foo");