As the title says, what are some ideas for dealing with non-API request related dependencies in a JMeter test?
I have a series of tests that work with zipped-up data. The first step in the test is to unzip that data. Clearly, this takes time - including it in the JMeter test captures the results of the call to unzip alongside everything else so skews the results. Similarly, I may need to do things with data after a series of tests that don't involve API calls.
In terms of a "script", they're definitely part of the overall test - I just think they should be in the JMeter test. I could write a powershell script (or something similar) to handle those elements, which I think would work fine for running in a CI/CD pipeline but be less usable when running locally (e.g. debugging or adding new steps/tests).
Any good mechanisms which'll work nicely in both scenarios?