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

Behat output double-counts scenarios

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide
      1. Initialize behat
      2. Run feature mod/workshop/tests/behat/workshop_assessment.feature with
        • --format progress --out std
        • --format moodle_progress --out std
        • --format moodle_progress --out std --format progress --out ~/test.txt
      3. Expected: stats in the last show 2 scenarios
      4. Current: (with both formatters), it show 4 scenarios.
      Show
      Initialize behat Run feature mod/workshop/tests/behat/workshop_assessment.feature with --format progress --out std --format moodle_progress --out std --format moodle_progress --out std --format progress --out ~/test.txt Expected: stats in the last show 2 scenarios Current: (with both formatters), it show 4 scenarios.
    • Affected Branches:
      MOODLE_31_STABLE
    • Fixed Branches:
      MOODLE_31_STABLE
    • Pull Master Branch:
      wip-mdl-55380

      Description

      When running behat test with Moodle 3.1 (Behat 3), the steps are run correctly, but the number of scenarios reported at the end is doubled. This seems to be a bug in the output formatter.

      Step to reproduce on master (from David Mudrak):

      1. Add "@testme @javascript" tags to mod/workshop/tests/behat/grade_to_pass.feature
      2. Run behat with --tags=testme
      3. Watch the tests run in the browser to verify that each of the 5 scenarios is run only once.
      4. Expected result: the end of the output shows: 5 scenarios (5 passed) 72 steps (72 passed)
      5. Actual result: the end of the output shows: 10 scenarios (10 passed) 124 steps (124 passed)

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  12/Sep/16