Nolana - Bulk Edit Performance testing
Modules needed
ui-users
ui-inventory
mod-inventory-storage-modules
ui-bulk-edit
mod-data-export worker
mod-data-export-spring
Testing expectations
Bulk edit user records
Bulk edit item records with the updates to locations and statues
Run multiple bulk edits concurrently
Run bulk edit while exporting:
circulation logs
bursar data
EDIFACT
eHoldings
Demo
User records - in app approach:
Item records:
Holdings records:
Bulk edit testing setup
User records testing scenarios
User status updates
Upload file with user barcodes
Click Start bulk edit option in Action menu and make following changes
Set patron group to <value available on test environment>
Set expiration date to November 1, 2025
Replace ".com" with ".org" in the email box
Confirm the changes
Commit the changes
Verify the changes are correct
Download the file with updated records
Download the file with errors (if applicable)
Item records updates:
Upload file with item barcodes
Click Start bulk edit option in Action menu and make following changes:
Set Temporary location to Clear field
Set Permanent location to < to the value available on test environment>
Set Status to Unknown
Set Temporary loan type to Clear field
Set Permanent loan type to < to the value available on test environment>
Confirm the changes
Commit the changes
Verify the changes are correct
Download the file with updated records
Download the file with errors (if applicable)
Holdings records updates:
Upload file with HRIDs
Click Start bulk edit option in Action menu and make following changes:
Set Temporary location to Clear field
Set Permanent location to <to the value available on test environment>
Confirm the changes
Commit the changes
Verify the changes are correct
Download the file with updated records
Download the file with errors (if applicable)
Concurrent and consecutive tests:
Each of the following scenarios to be tested separately. Scenarios are ordered by priority
Scenario 1. Run simultaneously bulk edits:
one job for 2500 user records
one job for 10k item records
(If possible ramp up the number of records to 5k and 100k for users and items respectively)
Scenario 2. Run simultaneously bulk edits:
one job for 2500 user records
one job for 10k holdings records
(If possible ramp up the number of records to 5k and 100k for users and items respectively)
Scenario 3. Run consecutively four jobs editing 2500 user records
Scenario 4. Run consecutively four jobs editing 10k item records
Scenario 5. Run simultaneously four jobs editing 2500 user records
Scenario 6. Run simultaneously four jobs editing 10k item records
Scenario 7. Run simultaneously four jobs editing 10k holdings records
Failover tests:
Determine likelihood of failover
Determine that the tasks restart
Determine that the new task picks up the jobs that were in progress