Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Merge new workflow to the existing JMerer script
  2. The new workflow should be added as 1 new thread (transform it if needed).
  3. Transform all Module controllers in the thread to Transaction controllers or Simple controllers to avoid future problems with script support (the new name of the test plan can cause all Module controllers unmapped)
  4. Ensure that all config elements are the same for all workflows and delete duplicates. If there are distinct, special ones for the new workflow move them inside the workflow thread.
  5. Configure thread parameters with variables named with prefixes according to the workflow naming. Example duration for check-in/check-out - CICO_duration.
    Add this variable to User Defined Variables as a Property to be able config settings for test runs from Jenkins.
  6. Prepare JMeter-supported data files: Define which data should be distinct and prepare specific files and place them in the jmeter-supported-data folder.

General recommendations for script creation

  1. Avoid using Module controllers
  2. Sharing mode for CSV data set config in JMeter: Current thread or Current thread group
  3. Use prefixes according to the workflow naming for variables. Example duration for check-in/check-out - CICO_duration.
  4. For data preparation: make sure that for loan renewal, CICO, and for items bulk editing (the list can be increased) we need unique items and users' barcodes.
  5. Need to analyze the distribution for each of the workflows

Database population script should be prepared

As an example of the script, we can use the existing one for the check-in/checkout workflow on Carrier.io.

Drawio
bordertrue
diagramNameWorkflows Diagram
simpleViewerfalse
width
linksauto
tbstyletop
lboxtrue
diagramWidth1241
revision1

...