Add tests for window reload assertions and update API contracts & fakes

[AdrianDev374]

🧩 Description

Added support for testing window reload actions in WindowManagerFake.
Before this change, the fake only handled open, close, show, and hide, so we couldn’t verify when a component called Window::reload().

🚀 What’s new

• Added a reload() method to record reload actions.
• Added two new assertions:
• assertReloaded() – checks if a window was reloaded (optionally by ID).
• assertNotReloaded() – checks that no reload happened.
• Updated tests to use the new assertions.

[gwleuverink]

Hey @AdrianDev374 Thank you for your contribution!

This is looking great 🙏🏻 I ran into a tiny problem, which is not limited to what's added in this PR, but also exist on the other assertion methods.

If we call refresh without any arguments it will automatically detect the current window eg Window::reload(). So no arguments are required here.

The assertion however expects it to be given input. So this fails: Window::assertReloaded()

I can fix this by making the id argument null by default. But it might be good to think about what's expected here.

If you call Window::assertReloaded() without any argument would you expect this to assert the current window was reloaded or should we assert any window was reloaded?

[AdrianDev374]

Hi @gwleuverink

In my opinion, it would be nice if the ID is null, it checks if the current window has been reloaded, and if an ID is passed, it checks if that window has been reloaded.

In my application, I work with multiple windows, and I think it might be more interesting to be able to see if a specific window has been reloaded.

[AdrianDev374]

Hey @gwleuverink

if ($id === null) {
      $id = $this->current()->getId();
}

Maybe adding this and making the id of the assert nullable.