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

Behat failure with clean running @block_timeline

    XMLWordPrintable

    Details

      Description

      This is a followup of MDL-63044 where the block_timeline was introduced.

      It seems that we are getting some consistent (5/5) failures with the new block acceptance tests.

      Initially detected by an individual run, I've launched FIVE executions of @block_timeline with the clean suite and they are consistently failing:

      https://ci.moodle.org/view/Testing/job/DEV.01%20-%20Developer-requested%20Behat/317/

      Details:

      001 Scenario: All in date view                                                                                  # /var/www/html/blocks/timeline/tests/behat/block_timeline_dates.feature:56
            And I click on "[data-region='paging-bar'] [data-control='next']" "css_element" in the "Timeline" "block" # /var/www/html/blocks/timeline/tests/behat/block_timeline_dates.feature:67
              unknown error: Element is not clickable at point (907, 658)
                (Session info: chrome=66.0.3359.117)
                (Driver info: chromedriver=2.38.552522 (437e6fbedfa8762dec75e2c5b3ddb86763dc9dcb),platform=Linux 4.13.0-41-generic x86_64) (WebDriver\Exception\UnknownError)
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ryanwyllie Ryan Wyllie
                Reporter:
                stronk7 Eloy Lafuente (stronk7)
                Integrator:
                Andrew Nicols
                Tester:
                CiBoT
                Participants:
                Component watchers:
                Andrew Nicols, Mathew May, Michael Hawkins, Shamim Rezaie, Simey Lameze, Amaia Anabitarte, Carlos Escobedo, Sara Arjona (@sarjona), Víctor Déniz Falcón
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  3/Dec/18