Fix implementation of containsExactly

[koenpunt]

The implementation was the same for contains and containsExactly, but containsExactly should fail when the number items doesn't match the size of the expected items list.

[dugenkui03]

(a,b).containsExactly(a,a) will result in true in this pr.

org.assertj:assertj-core seems to be useful, but it is only allow in test.

[koenpunt]

(a,b).containsExactly(a,a) will result in true in this pr.

Yes order isn't checked with this. But I don't think that's the purpose of this method.

If you want to assert the order, you can do so using isEqualTo;

In Kotlin (which looks a bit funky because generics can't be inferred):

.path("some[*].id")
  .entityList(String::class.java)
  .isEqualTo<GraphQlTester.ListEntitySpec<String>>(listOf("a", "b"))

Or in java:

.path("some[*].id")
  .entityList(String.class)
  .isEqualTo(Arrays.asList("a", "b"))

[rstoyanchev]

The terminology is aligned with AssertJ and there containsExactly is "contains exactly the given values and nothing else, in order". It would make sense to align the behavior too and I think the Javadoc could also use some improvement.

[koenpunt]

I've updated it to use equals, which does just that:

Compares the specified object with this list for equality. Returns true if and only if the specified object is also a list, both lists have the same size, and all corresponding pairs of elements in the two lists are equal.