Skip to end of banner
Go to start of banner

Test data preparation

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

To prepare data for workflows data should be unique for each separate workflow.

To run all workflows:

credentials (variables or .csv file) needed for the environment being tested. Username, password, hostname, and tenant should be replaced by valid data.


Simultate Blacklight Requests (BLS)

The following data files are needed to support the Jmeter script during its execution.
- BLS_item_holdings_instance_ids.csv.csv: a list of item ids and their related holdings and instances to run the script. To obtain these UUIDs, run the following SQL script:

SELECT item.id as itemId, hr.id as hrId, hr.jsonb->>'instanceId' as instanceId 
FROM {tenant}_mod_inventory_storage.item item
INNER JOIN {tenant}_mod_inventory_storage.holdings_record hr
ON uuid(item.jsonb->>'holdingsRecordId') = hr.id
WHERE item.jsonb->'status'->>'name' = 'Available'
LIMIT 1000


- BLS_user_ids.csv: a list of user ids to run the script. These are users who are active and have a valid barcode.

View Patron Record (PRV)

The following data files are needed to support the Jmeter script during its execution.
- user_ids.csv: a list of UUIDs and names of actual users that will be used to execute the script.

Check-in Check-out (CICO)

The following data files are needed to support the Jmeter script during its execution.
- Available.csv: a list of barcodes that have Available status
- checked_out.csv: a list of barcodes that although have Available status may be considered as "checked out" so that they can be used in the check-in calls.
- user_barcodes.scv: a list of barcodes of actual patron IDs that will be used to check in/out with.


Item level Requests (ILR)

The following data files are needed to support the Jmeter script during its execution.
- itembarcodes.csv: a list of barcodes that have Available status
- user_barcodes.scv: a list of barcodes of actual patron IDs that will be used to check in/out with.


Monitoring Pick Slips Requests (MPS)

The following data files are needed to support the Jmeter script during its execution.
- servicepoints.csv: a list of service point ids. It will be used to execute /circulation/pick-slips/<servicepointId> requests.

SELECT id FROM


Data export (DE)

The following data files are needed to support the Jmeter script during its execution.

-A proper job profile should be configured or added to the environment

-A set of files with item IDs, holdings IDs, or/and instance IDs should be prepared.

For example: 

SELECT id FROM {tenant}_mod_inventory_storage.instance where jsonb->>'source'='MARC' LIMIT 40;


Data Import (DI)

- Prepare files with proper naming. Do not use dashes (-) in file names:
                        bib_Create should be included in the file name for MARC BIB Create
                        holdings_Create should be included in the file name for MARC Holdings Create
                        authority_Create should be included in the file name for MARC Authority Create

                        or another naming according to specific profiles
- Ensure that the environment has proper job profiles.


Fiscal Year Rollover (FYR)

The following data files are needed to support the Jmeter script during its execution.
- ledgers_ids.scv: a list of keywords for searching ledger and id

SELECT {tenant}_mod_finance_storage.ledger.jsonb->'name', id
  FROM {tenant}_mod_finance_storage.ledger;

Use preparation script to generate data for FYR (FY_rollover_preparation.jmx).

Ledger Operations (LO)

The following data files are needed to support the Jmeter script during its execution.
- keywords.scv: a list of keywords for searching ledger and id

SELECT {tenant}_mod_finance_storage.ledger.jsonb->'name', id
  FROM {tenant}_mod_finance_storage.ledger;


Edit Bib Record Tag Table Group (ETT)

- keywords.csv (contains keyword) in this case it is Instance keyword you can generate this file using scripts/selectKeyWords.sql

SELECT substring((({tenant}_mod_inventory_storage.instance.jsonb)->'title')::TEXT from 2 for 4),ARRAY_AGG({tenant}_mod_inventory_storage.instance.id)
FROM {tenant}_mod_inventory_storage.instance
INNER JOIN {tenant}_mod_inventory.records_instances
ON {tenant}_mod_inventory_storage.instance.id = {tenant}_mod_inventory.records_instances.instance_id
INNER JOIN {tenant}_mod_source_record_storage.raw_records_lb
ON {tenant}_mod_inventory.records_instances.record_id = {tenant}_mod_source_record_storage.raw_records_lb.id
group by substring((({tenant}_mod_inventory_storage.instance.jsonb)->'title')::TEXT from 2 for 4)
having count(1) > 3 and count(1) < 10;












  • No labels