Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
eHoldings Sprint 110
-
3
-
Spitfire
Description
This story is aimed to verify that load holding process is stable before the Q4 release.
Requirements:
setup a separate environment for the testing purpose (existing Vagrant boxes can be used) and perform several runs with following conditions:
- more than one tenant is created
- more than one credentials available for tenant
- XX:+HeapDumpOnOutOfMemoryError is added
Proposed setup(s):
- one tenant and several credentials(3-5)
- two tenants with several credentials(3-5) for each tenant
Acceptance criteria:
- logs for run are attached
- environment info(JDK version, memory, etc.)
Additional information:
In the previous releases 'mod-kb-ebsco-java' module had several issues during the loading process and one of them is MODKBEKBJ-528.
TestRail: Results
Attachments
Issue Links
- defines
-
FHIQC-10 Load Holdings: Refactor using of Vert.X WebClient
-
- Closed
-
-
MODKBEKBJ-575 Load Holdings: Failed to update holdings_status
-
- Closed
-
-
MODKBEKBJ-577 Load Holdings: Decrease size of loading pages
-
- Closed
-
- mentioned in
-
Page Loading...