Details

    • Testing Instructions:
      Hide

      Prerequisites

      Download and install ngrok and run it with

      ngrok http 80

      Set your wwwroot to use that url. e.g. https://asdfasdf.ngrok.io/integration_master/

      1. As admin: (Test in all browsers, except the last two steps)
        1. Go to "Site administration > Plugins > Activity modules > LTI > Manage tools"
        2. Add a tool using only the launch url (old interface) by clicking on 'configure a tool manually.'
        3. Add a tool using an xml cartridge (e.g. from eduappcenter.com - you need to visit this site to get the URL you need, eg. https://www.edu-apps.org/lti_public_resources/config.xml?id=youtube)
        4. Add a tool using the configuration url (LTI2)
          1. https://online.dr-chuck.com/sakai-api-test/tp.php or http://lti.tools/test/tp.php
        5. Remove a tool using the x button on the card
        6. Enter a url that does not exist, make sure you recieve a message that it is having trouble loading after 20 seconds
        7. Enter a url to an xml file that is not a cartridge, make sure you get an error ( http://www.w3schools.com/xml/note.xml )
        8. Edit a tool that was made via a cartridge url using the cog button on the card
        9. Edit a tool that was made via the configuration url using the cog button on the card
      2. As a teacher (Test the first 3 steps in all browsers).
        1. Add an external tool to a course
        2. Set the launch URL/cartridge URL to a cartridge (e.g. from eduappcenter.com)
        3. Ensure you get the green tick and it says a cartridge will be used
        4. Click save changes
        5. Make sure the external tool is now set up using the settings from the cartridge
        6. Add another external tool to a course
        7. Set the Launch URL to the url used by one of the tools you added as an admin
        8. Ensure you get a green tick
        9. Save changes
        10. Ensure the settings you configured as an admin are used
        11. Add another external tool to a course
        12. Set a url to any site you didn't add as an admin. Ensure you get a yellow warning saying that no configuration was found.
        13. Save changes
        14. Add another external tool to a course
        15. On the settings page, click the plus to add a tool type.
        16. In the popup, put a cartridge url into the "tool base url/cartridge url" text box
        17. Press save changes on that popup
        18. Press save and display
        19. Make sure the tool works, and correct tool is displayed
      Show
      Prerequisites Download and install ngrok and run it with ngrok http 80 Set your wwwroot to use that url. e.g. https://asdfasdf.ngrok.io/integration_master/ As admin: (Test in all browsers, except the last two steps) Go to "Site administration > Plugins > Activity modules > LTI > Manage tools" Add a tool using only the launch url (old interface) by clicking on 'configure a tool manually.' Add a tool using an xml cartridge (e.g. from eduappcenter.com - you need to visit this site to get the URL you need, eg. https://www.edu-apps.org/lti_public_resources/config.xml?id=youtube ) Add a tool using the configuration url (LTI2) https://online.dr-chuck.com/sakai-api-test/tp.php or http://lti.tools/test/tp.php Remove a tool using the x button on the card Enter a url that does not exist, make sure you recieve a message that it is having trouble loading after 20 seconds Enter a url to an xml file that is not a cartridge, make sure you get an error ( http://www.w3schools.com/xml/note.xml ) Edit a tool that was made via a cartridge url using the cog button on the card Edit a tool that was made via the configuration url using the cog button on the card As a teacher (Test the first 3 steps in all browsers). Add an external tool to a course Set the launch URL/cartridge URL to a cartridge (e.g. from eduappcenter.com) Ensure you get the green tick and it says a cartridge will be used Click save changes Make sure the external tool is now set up using the settings from the cartridge Add another external tool to a course Set the Launch URL to the url used by one of the tools you added as an admin Ensure you get a green tick Save changes Ensure the settings you configured as an admin are used Add another external tool to a course Set a url to any site you didn't add as an admin. Ensure you get a yellow warning saying that no configuration was found. Save changes Add another external tool to a course On the settings page, click the plus to add a tool type. In the popup, put a cartridge url into the "tool base url/cartridge url" text box Press save changes on that popup Press save and display Make sure the tool works, and correct tool is displayed
    • Affected Branches:
      MOODLE_31_STABLE
    • Fixed Branches:
      MOODLE_31_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      MDL-52154-master-wip2

      Description

      E.g. There is no point listing the capabilities, before we know what capabilities the tool requires.

      Allow admins to create and approve tools in one step.

      There is no point in 2 separate list of pending tools.

      Look everywhere and remove as many steps out of every process as possible.

      List of required changes

      1. Combine the two pages
        1. Manage external tool types
        2. Manage external tool registrations
      2. Remove pending state (we left it while a user decides whether they want to accept capabilities)
        1. Tool created through "Tool Registration" should be added to tool type immediately
        2. Tool added through tool type should be added immediately
      3. Just one tool add screen. Determine what the url given is
        1. XML, use our new xml parser
        2. Tool registration URL register automatically
        3. Tool launch URL, add the tool type (will require extra screen to fill in more details)
      4. In tool proxy tool registration, do not list capabilities until after firing the Registration request

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Votes:
                  1 Vote for this issue
                  Watchers:
                  15 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    23/May/16