How To
BadgeTest lets you issue badges to the Backpack instance of your choosing. It's great for testing the badge acceptance flow, or chucking a couple badges into a Backpack if /demo/ballertime isn't your cup of tea.
BadgeTest is deployed at http://badgetest.herokuapp.com.
The full interface, showing advanced options:
The most basic options for issuing test badges is the number of badges to issue, to which email, on which server, using which method.
- number of badges: each badge currently has the same graphic, but will have a unique name.
- which email: you will need to log in to the Backpack with the same email address for the issuance to succeed. You can force an error by purposefully using a mismatching email.
- which server: by default, the Open Badges development, staging, and production servers are available as options. Please note that the Go button will not be available if the Issuer API was not successfully loaded from your server of choice.
- which method: modal, modaless, or Backpack Connect. Only options supported by the selected server will be shown.
Additional checkboxes are provided to toggle certain behaviors.
- hash email: this will hash the email address in the badge assertion, which is now the preferred form according to the OBI metadata spec.
- don't uniquify: this will allow you to submit an identical badge twice (or more times), thereby forcing an error.
- generate images: this allows you to generate unique badge images based on the badge name. It uses vanillicons, so they're adorable to boot.
Make your selections for the above items, and click Go!
Under the advanced options, you can add additional Backpack servers from which to fetch the Issuer API.
- name: the identifier to appear in the dropdown.
- issuer.js url: most likely /issuer.js.
You can remove individual servers from your list, or reset the entire list as well.
Your server preferences are saved in localStorage, so they should be there for you later.