This epic covers any improvements necessary to our clients, servers, and processes to support the functionminmg of an integrated test system.

This epic does not cover the creation of the integration tests themselves, or what happens after the tests run – only the prerequisites that will allow the tests to run in the first place.

Here are some of the high-level requirements we've identified thus far.

• When a change is merged into the mobile codebase, new binaries for all relevant apps are built and placed in a location where the integrated test system can pick them up.
  • At a minimum, this includes the SimplyE mobile app and a "vanilla" app that works just like SimplyE but contains no DRM secrets and no code that is not oipen source.
• A similar build process should be put into place for the circulation-patron-web web-based client.
• Integration tests are able to use a variety of test credentials against a variety of real servers and real libraries, as necessary to fulfill the purpose of the test.
• Integration tests are able to operate on different types of data without having to hope that the server sends them appropriate data.
• As much as possible, integration tests are run through the standard mobile interface accessible to human end-users, and do not require special lower-level access to mobile APIs.

This epic comes out of the "jackpot feed" spike (https://jira.nypl.org/browse/SIMPLY-2973)