I converted an existing NeoLoad 5.1.4 test to NeoLoad 5.2.2.
After the conversion i changed runtime parameters:
When an error occurs: Do nothing
When an assertion failes: Go to next iteration.
When i run the test, both in check and normal run mode the test does not stop/go to next iteration after an assertion failes.
This is a known issue that has just been discovered. It will be fixed in patch 5.2.3 that should be out next week.
As a workaround you can include your whole script inside a Try container and use a "Go to the next iteration" action in the cache container.
Then configure your Try container to catch assertion error.
