Done
Details
Assignee
Aliaksei HarbuzAliaksei HarbuzReporter
Magda ZacharskaMagda ZacharskaPriority
P3Story Points
3Sprint
NoneDevelopment Team
FirebirdTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Aliaksei Harbuz
Aliaksei HarbuzReporter
Magda Zacharska
Magda ZacharskaPriority
Story Points
3
Sprint
None
Development Team
Firebird
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 5, 2022 at 12:14 AM
Updated November 2, 2022 at 9:36 PM
Resolved November 2, 2022 at 9:36 PM
Purpose/Overview:
Establish a baseline for bulk edit app - item records update.
Requirements/Scope:
Create jmeter tests that can be executed against: https://bulk-edit-perf.ci.folio.org/
The tests cover item status updates for following statuses:
Available
Missing
Withdraw
the test will start with 100 item records edits and then progress to 1000 records edits and then 10 000 and 100 000 records edits
the test will cover scenarios when the bulk edit is triggered by uploading file with following identifiers:
item barcodes
item UUIDs
holdings UUIDs
item HRIDs
item former ids
item accession numbers
the test will cover saving records preview and saving matching records in CSV format
the test will cover impact of the bulk edit on the inventory modules documented: CPU, memory, db timeouts
Approach:
Acceptance criteria:
The tests are written and can be executed on demand
The findings are documented on the wiki
Additional information:
Coordinate with devops to get memory/cpu usage