Uploaded image for project: 'Moodle QA'
  1. Moodle QA
  2. MDLQA-325 Moodle QA non-runners
  3. MDLQA-17863

CLONE - An admin can create a backpack using OpenBadges v2.1 OAuth service and users can send their badges to this backpack

XMLWordPrintable

    • Icon: Functional Test Functional Test
    • Icon: Minor Minor
    • Moodle 4.2
    • Moodle 4.2
    • Badges, Student
    • None

      Requirements

      • A site with public access run with HTTPS where you can log in as admin. If you would like to use the QA testing site for running it, please see the QA testing guide for details on how to request admin access. Begin just after the hourly reset to give yourself plenty of time to complete the test!
      • A badgr account on https://eu.badgr.com/ (Europe).

      Setup badges

      1. Login as admin.
      2. Go to "Site administration | Badges | Add a new badge" and create a badge at site level.
      3. Add criteria to the badge so it can be manually issued by role.
      4. Enable the badge.
      5. Issue the badge to any user (student1).

      Testing scenario 1: Create Open Badges service and backpack

      1. Login as admin.
      2. Go to "Site administration / Server / OAuth 2 services".
      3. Create an "Open Badges" service with the following information:
      4. Check "Client ID" and "Client secret" fields are not mandatory and "Service base URL" is mandatory.
        • There is no need to check the "Scopes included in a login request" fields. They should be filled in automatically.
      5. Save changes. 
      6. Check the "Discovery" column in the OAuth2 services table has a green tick mark for the "Badgr Europe" service created.
      7. Access to the "Configure endpoints" page.
      8. Check, at least, the following endpoint appears: discovery_endpoint
      9. Edit the "Badgr Europe" service.
      10. Check the "Client ID" and "Client secret" fields are not empty.
      11. Go to "Site administration / Badges / Manage backpacks".
      12. Click the "Add a new backpack" button and create a new backpack with the following information:
      13. Save changes.

      Testing scenario 2: Connect to backpack

      1. Login as a user with at least one badge awarded (student1).
      2. Go to Dashboard / Preferences / Badges / Backpack settings.
      3. Select "https://eu.badgr.io/" as "Backpack provider".
      4. Check the "Status" is "not connected" and the button "Connect to backpack" appears.
      5. Click the button "Connect to backpack".
      6. Check the site is redirected to the backpack site and the login form is displayed.
      7. Login using one Badgr Europe existing user.
      8. Check the screen requesting your permission is displayed with the following application access permissions:
        • Get Open Badges Profile
        • Create Open Badges Assertion
        • Get Open Badges Assertions
        • Offline Access
      9. Click the button "Yes, Allow".
      10. Check the "Backpack has been connected" message is displayed.
      11. Check you're redirected to the Manage badges page.
      12. Click the "Change backpack settings" button.
      13. Check the status is "Connected".

      Testing scenario 3: Send badge to the backpack

      1. Go to Dashboard / Preferences / Badges / Manage badges.
      2. Click on the "Add to backpack" button.
      3. Check the message "Added badge to backpack " is displayed.

        1. MDLQA-17863_1_1.png
          MDLQA-17863_1_1.png
          214 kB
        2. MDLQA-17863_1_2.png
          MDLQA-17863_1_2.png
          110 kB
        3. MDLQA-17863_2_1.png
          MDLQA-17863_2_1.png
          137 kB
        4. MDLQA-17863_2_2.png
          MDLQA-17863_2_2.png
          162 kB
        5. MDLQA-17863_3.png
          MDLQA-17863_3.png
          37 kB

            andelacruz Angelia Dela Cruz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:

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