Overview
API tests exist and are maintained on an ongoing basis for a decent cross-section of FOLIO modules. However, these tests are not run as part of the regular community CI process. I believe doing so would be an easy way to provide early warning that there are integration level problems.
For instance, mod A depends on mod B's interface v1.0. Mod B makes some breaking changes but forgets to increase the major interface version - or doesn't realize its a breaking change. As a result mod A is broken or misbehaving, but since it's not actively being developed or tested anymore this turns into an escape defect... oops!
Approach
- May be run the API tests (if they exist) against folio-testing or folio-snapshot on a daily basis, outside of the daily build/deployment process.
- Ideally notifications could be setup so that a team or the responsible maintainer is notified tests fail.
- * Alternatively, a dashboard that reports API test pass/fail status w/ links to run logs would probably suffice.
Acceptance Criteria
- Existing API tests are run on a periodic (daily?) basis
|