[FOLIO-630] Incorporate API-level integration tests into Github PR for backend FOLIO modules Created: 24/May/17 Updated: 12/Nov/18 Resolved: 08/Nov/17 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | ci | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Sprint: | |||||||||||||||||
| Description |
|
Add "partial" integration tests to Jenkins PR-triggered jobs. At a minimum, partial integration testing should include the module's external storage component (if applicable), the current stable release of Okapi, direct module dependencies, and API-level tests. |
| Comments |
| Comment by John Malconian [ 24/May/17 ] |
|
Start with mod-inventory and mod-inventory-storage as test cases. Test in new branch of those projects. |
| Comment by John Malconian [ 08/Nov/17 ] |
|
This level of testing is best implemented by developers of the modules as needed. |