Hi,
Loving using K6 it really makes writing load testing easy! I have built out a framework for delivering building block endpoint benchmark/load tests that can then be composed using the fantastic scenarios into realistic load testing for various testing scenarios. It works a charm and outputs the data to our database for tracking purposes. The only slight fly in the ointment is that if a test gets terminated the handleSummary still gets called and spurious results get written to the database polluting our tracking solution. There does not appear to be any way to determine that the scenario has been terminated in the summary results themselves. Any suggestions on how I can filter out these spurious runs?
thanks in advance
1 post - 1 participant
