Summary

ShouldContainOnly is used in a few places where we know what kind of elements we are dealing with, in this case instead of using the term element we could use a more descriptive name.

Example

Spliterator<?> actual = createSpliterator(SORTED | ORDERED);
spliterators.assertHasOnlyCharacteristics(INFO, actual, DISTINCT, SORTED);

fails with this error

Improve documentation in terms of javadoc and website as well. Where feasible introduce minor code changes for better readability.

Here's a non exhaustive list, feel free to add a comment to add items to this list.

• navigation assertions limitation (not strongly typed)
• Set assertions contains
• ...

Move the code and dependencies out of justtestlah-core into justtestlah-applitools and justtestlah-galen.

We also need to write unit tests for these integrations.

• isConstraintIndex
• isNotConstraintIndex

According to the method name and it's documentation I expect assertThat(emptyMap()).containsOnlyKeys("x") to NOT fail.

There's one example in the Javadoc that helps me understand the real semantics. However, I'd like to see that also in the text above, and ideally in the method name.

Related: https://math.stackexchange.com/questions/202452/why-is-predicate-all-as-in-allset-true-if-the-set-