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

Failures with behat and classic on LTI completion scenarios

    XMLWordPrintable

    Details

      Description

      Since some hours ago we are getting consistent failures with the feature / scenario:

      View activity completion information in the LTI activity / Use manual completion
      

      Only with classic, but consistently.

      Link: (ignore the other error) https://ci.moodle.org/job/W.07.01%20-%20Behat%20-%20Firefox%20+%20Postgres%20+%20Classic/575/

      --- Failed steps:
       
      001 Scenario: Use manual completion                                    # /var/www/html/mod/lti/tests/behat/lti_activity_completion.feature:63
            And I navigate to "Edit settings" in current page administration # /var/www/html/mod/lti/tests/behat/lti_activity_completion.feature:67
              Xpath matching locator "//section[contains(@class,'block_settings')]//div[@id='settingsnav']/ul[1]/li[1]/p[1]/span" not found. (Behat\Mink\Exception\ElementNotFoundException)
      

      Looking to the code, this scenario was added by MDL-71161, so assuming it's a regressions there.

      Ciao

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              michaelh Michael Hawkins
              Reporter:
              stronk7 Eloy Lafuente (stronk7)
              Peer reviewer:
              Huong Nguyen Huong Nguyen
              Integrator:
              Eloy Lafuente (stronk7) Eloy Lafuente (stronk7)
              Tester:
              CiBoT CiBoT
              Participants:
              Component watchers:
              Sam Marshall, Amaia Anabitarte, Carlos Escobedo, Ferran Recio, Ilya Tregubov, Sara Arjona (@sarjona), Adrian Greeve, Jake Dallimore, Mathew May, Mihail Geshoski, Peter Dias, Sujith Haridasan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Fix Release Date:
                17/May/21

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 hours, 10 minutes
                  3h 10m