implement findAll to allow fluent assertions against all elements that match selector

[FRFlor]

Purpose

Hello there 👋,

I believe that, at the moment, the way to make assertions against multiple matches is done through $assertElement->contains() and $assertElement->doesntContain() methods.

The limitation of these approaches is that the contains() doesn't allow us to write an assertion that ensures all elements under a given selector respect a specific set of rules.

For example:
"Assert all images being rendered have an 'alt' attribute"

->assertElementExists(fn(AssertElement $viewRendered) => viewRendered
    ->doesntContain('img', [???]) // Without alt attribute

I believe we cannot perform this assertion with the existing resources. Let me know if I'm mistaken.

My proposed solution is the following:

---

The reasoning behind this proposal is two-fold:

• It allows us to make sweeping assertions about what must be enforced for all elements in the selection.
• It allows us to continue making fluent assertions over all elements in the selection

• It resembles the ->has->each() API that exists in the FluentJSON assertion

---

I hope this doesn't go against the philosophy of the package.
I'm looking forward to any feedback or suggestions.

[sinnbeck]

Thanks for the PR!
I love the idea, but perhaps just name it each like with AssertableJson. That would make it much easier to remember :)

[FRFlor]

I love it, sounds good

Thanks for the PR! I love the idea, but perhaps just name it each like with AssertableJson. That would make it much easier to remember :)

Awesome 🎉! I'm glad you liked it!

Good point! Naming it each() makes it more descriptive.

[FRFlor]

@sinnbeck While I was updating the readme, I noticed there was a section of it using contains() with a callback being passed as an argument:

I think this is probably from an older version of the API. At the moment the contains does not take callbacks.

I included a quick tweak to this section to this instead:

But let me know if you would prefer me to revert this change. This is in the HEAD commit of the PR, I could just remove it.

[sinnbeck]

Oh nice catch! Normally I would prefer it in a separate PR but I will just release it as part of the same version :) Ill draft a new release right away