Steps to reproduce:

1. In Zabbix frontend, configure custom timeout for "Scheduled report test" in Administration > General > Timeouts. Alternatively, Zabbix API may be used. However, I have not checked whether it works or not.

Result:

The value is written into the database to "config.report_test_timeout". However, it is not used in Zabbix server code (except the upgrade patch). This way, it does not affect anything.

At the same time the value is documented here as if it affected something.

Expected:
The parameter should do something meaningful and should be properly documented or removed. It should be decided how this should be fixed.

As proposed by wiper:

There certainly is merit in having customizable timeout for tests... but that probably should be done in test report form.