This fix prevents website event tests from failing when optional sample or public user data is not installed. It helps keep automated checks stable across leaner setups, reducing false failures for teams validating releases.

Demo / Portal / Public do not necessarily exist.

Followup of odoo/odoo#129052

Runbot-60656
Runbot-60655

This update fixes Knowledge app test reliability by using existing test users instead of optional demo or portal users. It helps keep automated validation stable across environments where demo data may not be installed.

Runbot-56122

This update adjusts an internal appointment performance test so it works correctly when demo data is not installed. It helps avoid false failures in automated checks, keeping validation results reliable without changing user-facing appointment behavior.

There is an additional query in no-demo mode; let us avoid useless red runbots.

Runbot-62073

This fix updates an internal spreadsheet document test so it simulates a real button click more accurately. It helps keep automated checks stable and reduces false test failures without changing customer-facing features.

Before this commit, the test was not correctly simulating a click on the link chart button. This was due to the fact that the only event that was triggered was the pointerdown event, which is not enough to trigger the click event.

For an unknown reason, only triggering the pointerdown event has a side effect during the test to trigger an event handled in the Leatlef library, would lead to an error in the library, and thus in the test suite.

This commit fixes the issue by using the click helper function from the web client test helpers.

Runbot: 59203