Uploaded image for project: 'SimplyE 2.0'
  1. SimplyE 2.0
  2. SIMPLY-349

Add self-tests for all content integrations

XMLWordPrintable

    • S16 SIMPLY Jul26-Aug9, S18 SIMPLY Aug23-Sept6, S19 SIMPLY Sept6-Sept19

      As a site administrator, I want to run a self-test of any integration I've set up, so that I can a) verify that it's working b) understand what the problem is without having to ask for help.

      The components of this work:

      • Design an interface for self-tests – what method is called? How are results reported? How can we instrument the existing exceptions that are raised when an integration fails, so that when it fails as part of a self-test we can include diagnostic information about how to solve the problem? Does this integration even have a self-test? (core)
      • Implement self-tests for specific integrations. The highest priority integrations are Overdrive and the various ILS systems, since these are the ones that most frequently cause problems. But all integrations should have self-tests eventually, and all new integrations should require self-tests as part of their acceptance criteria. (core, circulation)
      • Implement a self-test interface in the admin interface. This is probably just a button that invokes the self-test and a way to see the results of the most recent self-test. (circulation-admin)

       Need to add description on how to test

            JosephDalton Joseph Dalton
            leonardrichardson Leonard Richardson [X] (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: