Quesnelia - Bulk Edit Performance testing -DRAFT

Modules needed

• ui-users
• ui-inventory
• mod-inventory-storage-modules
• ui-bulk-edit
• mod-bulk-operations
• 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

Bulk edit testing setup - compare with prior releases

• Files with user barcodes (100, 1000, 2500,5000)
• Files with item barcodes (100, 1000, 10 000, 100 000)
• Files with holdings HRIDs (100, 1000, 10 000, 100 000)
• Users configured with following permissions:
  •  Bulk Edit: (CSV) Edit and Bulk Edit: (CSV) View - for user records testing
  •  Bulk Edit: In ppp Edit and Bulk Edit: In app View - for user item records testing
• JMeter tests repository: https://github.com/folio-org/folio-perf-test/tree/master/Folio-Test-Plans/bulk-edit

Testing scenarios

1. User status updates
   1. Upload file with user barcodes
   2. Click Start bulk edit option in Action menu and make following changes
      1. Set patron group to <value available on test environment>
      2. Set expiration date to  November 1, 2025
      3. Replace ".com" with ".org" in the  email box
   3. Confirm the changes
   4. Commit the changes
   5. Verify the changes are correct
   6. Download the file with updated records
   7. Download the file with errors (if applicable)
2. Item records updates:
   1. Upload file with item barcodes 
   2. Click Start bulk edit option in Action menu and make following changes:
      1. Set Temporary location to Clear field
      2. Set Permanent location to < to the value available on test environment>
      3. Set Status to Unknown
      4. Set Temporary loan type to Clear field
      5. Set Permanent loan type to < to the value available on test environment>
      6. Add Administrative note by adding text: "This is a new administrative note"
      7. Add Action note by adding text: "This is a new action note"
      8. Add electronic access data
      9. Suppress from discovery (set the value to true)
   3. Confirm the changes
   4. Commit the changes
   5. Verify the changes are correct
   6. Download the file with updated records
   7. Download the file with errors (if applicable)
3. Holdings records updates:
   1. Upload file with HRIDs
   2. Click Start bulk edit option in Action menu and make following changes:
      1. Set Temporary location to Clear field
      2. Set Permanent location to <to the value available on test environment>
      3. Suppress from discovery (including option to suppress items)
      4. Add electronic access data
   3. Confirm the changes
   4. Commit the changes
   5. Verify the changes are correct
   6. Download the file with updated records
   7. Download the file with errors (if applicable)
4. Instance records updates
5. Query search 

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:

1. Determine likelihood of failover
2. Does tasks restart?
3. Does other task pick up the jobs that were in progress?

User records - in app approach:

Item records:

Holdings records: