chore: change to WebEnvironment.MOCK in tests.

[manolo]

It fixes migration to next vaadin version 24.4.x
See: vaadin/hilla#2169

[robertmcnees]

Hi @manolo! Is the webEnvironment parameter is required at all? Removing the parameter completely has no impact on the tests. Looking at MainViewTests, I can't see the need for a server to start.

The tests in MainViewTests (and also CrudWithVaadinApplicationTests) look like unit tests similar to these tests as referenced in this guide. These tests look different than the end to end tests defined in this class and this section of the guide that do require a server to start. I can't see any end to end tests in this repo.

If this issue shows up in 24.4, perhaps we can address this PR with an upcoming version bump of Vaadin. It looks like 24.4 is due out this month. What do you think?

[ZheSun88]

Hi, @robertmcnees here is the PR to upgrade this project to Vaadin 24.4, and it needs this fix to pass.
#115

[robertmcnees]

Thanks for the PR @manolo and the context @ZheSun88. I merged this PR so that the tests would pass when upgrading the Vaadin version to 24.4.1.

This repository is now managed by dependabot so if a scenario like this arises again we should be able to push additional commits to the dependabot PR when the CI build fails. Hopefully that makes our workflow easier to sustain going forward.

Thanks for your contribution!