Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-76774

Notice: Array to string conversion in lib/editor/tiny/tests/behat/behat_editor_tiny.php

XMLWordPrintable

    • MOODLE_402_STABLE

      While working on MDL-76691, I've faced the following behat error when running the "Enable/disable H5P options" scenario for TinyMCE with Chrome:

      Moodle 4.2dev (Build: 20221229), 12e9d9e1bf1291700fa0765116376ad2d02bf06b
      Php: 7.4.28, pgsql: 12.12 (Ubuntu 12.12-0ubuntu0.20.04.1), OS: Linux 5.4.0-132-generic x86_64
      Run optional tests:
      - Accessibility: No
      Server OS "Linux", Browser: "chrome"
      Started at 02-01-2023, 18:08
      .....................................................................F 70
      ----------------------------------------
      --- Failed steps:
      001 Scenario: Enable/disable H5P options                                                      # /home/sara/moodles/stable_master/moodle/lib/editor/tiny/plugins/h5p/tests/behat/h5p.feature:118
            And I click on the "Configure H5P content" button for the "Page content" TinyMCE editor # /home/sara/moodles/stable_master/moodle/lib/editor/tiny/plugins/h5p/tests/behat/h5p.feature:124
              Notice: Array to string conversion in /home/sara/moodles/stable_master/moodle/lib/editor/tiny/tests/behat/behat_editor_tiny.php line 198
      2 scenarios (1 passed, 1 failed)
      110 steps (69 passed, 1 failed, 40 skipped)
      1m12.72s (82.21Mb)
      
      

       

      It's passing locally with Firefox. 

      I use 3.141.59 selenium and 108.0.5359.94 (Official Build) (64-bit) Chrome. It's also failing when using headless. However, these tests are passing in the CI.

            Unassigned Unassigned
            sarjona Sara Arjona (@sarjona)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.