Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
2.7.1
-
MOODLE_27_STABLE
-
MOODLE_30_STABLE, MOODLE_31_STABLE
-
wip-mdl-46514
-
Description
Example is: code calls the non-existing function or tries to create an instance of non-existing class. PHP displays a fatal error. Behat test eventually fails on the next step when it can't find some text or button or link or whatever.
The failure message says : Can not find link/button/text. At the same time if you look at the screenshot of the step you can see that the PHP fatal error orange table is displayed with the backtrace. In case of a php warning/debugging message behat prints the backtrace in the console.
So there are two problems here:
1. More steps for developer to trace where the error occured.
2. If the error occurs on the last step of a scenario it is not caught by behat at all!
Attachments
Issue Links
- caused a regression
-
MDL-56865 PHP Notices thrown as fatal errors during Behat setup
-
- Closed
-
-
MDL-56978 Appears min_fix_utf8 is now emitting iconv notices
-
- Closed
-
- has a non-specific relationship to
-
MDL-54042 webservice core_user_get_users_by_field shows debugging: Undefined proprty
-
- Closed
-
-
MDL-54043 Duplicate index error during behat run
-
- Closed
-
-
MDL-50049 Phase 2 of deprecation of functions in lib/deprecatedlib.php in 3.0
-
- Closed
-
- is duplicated by
-
MDL-53995 Fatal errors not being detected by behat in master
-
- Closed
-
- will help resolve
-
MDL-53812 Stopping a behat execution breaks the behat test site
-
- Closed
-