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

Behat steps for selecting list items or table rows should match the inner-most

XMLWordPrintable

    • MOODLE_27_STABLE, MOODLE_28_STABLE
    • MOODLE_29_STABLE
    • Hide

      This really needs to be tested together with MDL-49446.

      1. Pull the latest MDL-40990 code.
      2. Edit mod/quiz/tests/behat/editing_require_previous.feature, the scenario "Question dependency cannot apply to quizzes where the questions are shuffled so UI is hidden" that starts around like 120
      3. Change shufflequestions to 0, so the test should fail.
      4. Run that senario, and verify that Behat reports the failure

      (Until I had fixed this, and #MDL-49446, it would not fail.)

      Show
      This really needs to be tested together with MDL-49446 . Pull the latest MDL-40990 code. Edit mod/quiz/tests/behat/editing_require_previous.feature, the scenario "Question dependency cannot apply to quizzes where the questions are shuffled so UI is hidden" that starts around like 120 Change shufflequestions to 0, so the test should fail. Run that senario, and verify that Behat reports the failure (Until I had fixed this, and # MDL-49446 , it would not fail.)

      Suppose you have nested lists like

      • Outer list item
        • Inner item 1
        • Inner item 2

      Then Behat steps like

      Then "Inner item 2" "list_item" ...

      will acutally match the Outer list item, since it looks for the first list item that contains "Inner item 2".

      I have a fix ni hand.

      The same applies to table_row.

            timhunt Tim Hunt
            timhunt Tim Hunt
            Rajesh Taneja Rajesh Taneja
            David Monllaó David Monllaó
            Adrian Greeve Adrian Greeve
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

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