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

Random failures in awarding badges scenarios completing competencies

XMLWordPrintable

    • MOODLE_37_STABLE, MOODLE_38_STABLE

      We have detected various random failures happening within badges/tests/behat/criteria_competency.feature.

      Links: https://ci.moodle.org/job/W.03.01%20-%20Behat%20-%20Chrome%20+%20Postgres/434/

      Here there are some cases (they affect to 2 scenarios and in 2 different places):

      001 Scenario: Award badge for completing a competency in the site # /var/www/html/badges/tests/behat/criteria_competency.feature:75
            And I press "Add competencies to course"                    # /var/www/html/badges/tests/behat/criteria_competency.feature:83
              stale element reference: element is not attached to the page document
      

      002 Scenario: Award badge for completing all competencies in the site # /var/www/html/badges/tests/behat/criteria_competency.feature:128
            Then I log in as "user1"                                        # /var/www/html/badges/tests/behat/criteria_competency.feature:178
              Field matching locator "'Username'" not found. (Behat\Mink\Exception\ElementNotFoundException)
      

      001 Scenario: Award badge for completing all competencies in the site # /var/www/html/badges/tests/behat/criteria_competency.feature:128
            And I press "Add competencies to course"                        # /var/www/html/badges/tests/behat/criteria_competency.feature:136
              WebDriver\Exception\StaleElementReference: stale element reference: element is not attached to the page document
      

            stronk7 Eloy Lafuente (stronk7)
            stronk7 Eloy Lafuente (stronk7)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

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