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

Behat test to confirm H5P activity can be duplicated (Automate MDLQA-14753)

XMLWordPrintable

    • 1
    • Team Hedgehog 2023 Review 4

      QA test to be automated: MDLQA-14753

      Testing instructions

      This is an exploratory test of a new feature or improvement, so please feel free to try anything you like and not just the test steps!

      Some H5P files attached to help with the testing.

      1. As a teacher go to a course and click on 'Turn editing on'.
      2. Click on 'Add an activity or resource'
      3. Select 'H5P' activity.
      4. Fill required 'Name' field and upload a .h5p file to 'Package file' (some .h5p files attached for testing.
      5. 'Save and display'
      6. Confirm the content is displayed with no errors.
      7. Confirm teacher can see 'This content is displayed in preview mode. No attempt tracking will be stored.'
      8. Go to the course and duplicate the just created H5P activity.
      9. Click on the duplicated H5P activity. 
      10. Confirm the content is displayed with no errors.
      11. Go to the course and delete duplicated activity.
      12. Click on the first created H5P activity. 
      13. Confirm the content is displayed with no errors.

            andelacruz Angelia Dela Cruz
            andelacruz Angelia Dela Cruz
            Raquel Ortega Raquel Ortega
            Simey Lameze Simey Lameze
            CiBoT CiBoT
            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 day, 1 hour, 1 minute
                1d 1h 1m

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