Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-49816 Random behat fails (old)
  3. MDL-50710

Bug in Behat test for random glossary block

XMLWordPrintable

      The "View random (last) entry in the glossary with auto approval" scenario (blocks/glossary_random/tests/behat/glossary_random.feature fails) fails:

      And I should not see "Concept1" in the "AutoGlossaryblock" "block" behat_general::assert_element_not_contains_text()
      "Concept1" text was found in the "AutoGlossaryblock" element

      The test runs too fast. This is what

      {behat_glossary_entries}

      looks like after success:

      mysql> select id,concept,definition,timecreated,timemodified from behat_glossary_entries;
      --------------------------------------------------

      id concept definition timecreated timemodified

      --------------------------------------------------

      210000 Concept1 Definition1 1435630762 1435630762
      210001 Concept2 Definition2 1435630763 1435630763

      --------------------------------------------------
      2 rows in set (0.00 sec)

      This is failure:

      mysql> select id,concept,definition,timecreated,timemodified from behat_glossary_entries;
      --------------------------------------------------

      id concept definition timecreated timemodified

      --------------------------------------------------

      210000 Concept1 Definition1 1435630693 1435630693
      210001 Concept2 Definition2 1435630693 1435630693

      --------------------------------------------------
      2 rows in set (0.00 sec)

            marina Marina Glancy
            cfulton Charles Fulton
            Rajesh Taneja Rajesh Taneja
            David Monllaó David Monllaó
            David Monllaó David Monllaó
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:

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