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

Need to execute init script twice when re-initialising Behat for parallel runs for upgraded instances

XMLWordPrintable

    • MOODLE_35_STABLE
    • MOODLE_34_STABLE, MOODLE_35_STABLE, MOODLE_36_STABLE
    • MDL-64597-master
    • Hide
      1. Checkout Moodle 3.4.0 

        git checkout v3.4.0

      2. Initialise parallel Behat. 

        php admin/tool/behat/cli/init.php -j=2

      3. Check out the appropriate branch for your Moodle instance. (e.g. if you're on 3.6, then you do a git checkout of the MOODLE_36_STABLE branch)
      4. Initialise parallel Behat again. 

        php admin/tool/behat/cli/init.php -j=2

      5. Confirm that after the database tables have been dropped, the process proceeds with the installation of the Behat sites right away.
      Show
      Checkout Moodle 3.4.0 git checkout v3.4.0 Initialise parallel Behat. php admin/tool/behat/cli/init.php -j=2 Check out the appropriate branch for your Moodle instance. (e.g. if you're on 3.6, then you do a git checkout of the MOODLE_36_STABLE branch) Initialise parallel Behat again. php admin/tool/behat/cli/init.php -j=2 Confirm that after the database tables have been dropped, the process proceeds with the installation of the Behat sites right away.

      What happens:

      1. Moodle instance with parallel Behat sites is set up.
      2. Moodle code base gets updated.
      3. Run init script: 

        php admin/tool/behat/cli/init.php -j=N

      4. Expected: The script should drop all the tables and reinstall the Behat sites.
      5. Actual: The script only drops the outdated tables and you have to run the script again in order to reinstall the Behat sites.

        1. image-2019-02-13-15-31-38-337.png
          image-2019-02-13-15-31-38-337.png
          320 kB

            jpataleta Jun Pataleta
            jpataleta Jun Pataleta
            Mathew May Mathew May
            Andrew Lyons Andrew Lyons
            Janelle Barcega Janelle Barcega
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 hour
                1h

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