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

Edit post as student scenario fails using slow servers/clients

    Details

    • Testing Instructions:
      Hide
      1. Run the whole suite (will be done automatically by the CI server, but confirm with integrators that it ran and finished with a 100% success)
      2. Edit a scenario of any of the codebase feature files without the @javascript tag
        • Add a custom @MDL-40246 tag in the preceding line of that scenario
        • Add a And I wait "3" seconds in the when or then sections of the scenario
        • Save the file
      3. Run behat using --tags @MDL-40246 option
      4. You SHOULD see a failure and the message SHOULD state that Waits are disabled in scenarios without Javascript support
      Show
      Run the whole suite (will be done automatically by the CI server, but confirm with integrators that it ran and finished with a 100% success) Edit a scenario of any of the codebase feature files without the @javascript tag Add a custom @ MDL-40246 tag in the preceding line of that scenario Add a And I wait "3" seconds in the when or then sections of the scenario Save the file Run behat using --tags @ MDL-40246 option You SHOULD see a failure and the message SHOULD state that Waits are disabled in scenarios without Javascript support
    • Affected Branches:
      MOODLE_25_STABLE, MOODLE_26_STABLE
    • Fixed Branches:
      MOODLE_25_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      MDL-40246_master

      Description

      Detected when using saucelabs, which adds a network delay + their VMs delay; to edit a forum discussion as a student takes around 25 seconds when running locally, and around 1 minute + 20 seconds using saucelabs through the CI server.

      With MDL-40123 integrated we save a few seconds but is not enough to provide stability.

      The problem comes with Edit forum post scenario of mod/forum/tests/behat/edit_post_student.feature, we set the site with a 1 minute to edit posts, but the process takes more than one minute, so an exception is thrown and the scenario fails. As we are not testing something related with javascript, I would propose to switch from @javascript to a goutte driver test (headless without JS).

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    8/Jul/13