You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now go-ftw executes requests one by one and then pull logs expecting the output to so the assertion.
While this is good, sometimes you want to profile and/or measure performance with close to real test data and go-ftw is a good option for this.
I wish go-ftw includes an option where N requests can be sent concurrently. This would allow to collect profiling data to debug latencies when evaluating and triggering rules.
The text was updated successfully, but these errors were encountered:
@jcchavezs While taking a look at this one, it is not clear if we are targeting running the same test N times, of just running the tests using N different threads. What did you have in mind?
My idea is that you could run N similar requests at the same time in a concurrent way. About logs, I think this would require the WAF connector to return the transaction ID in a response header so FTW can look for it specifically in the audit logs (@airween has a similar use case about returning the transaction ID in a response header).
Right now go-ftw executes requests one by one and then pull logs expecting the output to so the assertion.
While this is good, sometimes you want to profile and/or measure performance with close to real test data and go-ftw is a good option for this.
I wish go-ftw includes an option where N requests can be sent concurrently. This would allow to collect profiling data to debug latencies when evaluating and triggering rules.
The text was updated successfully, but these errors were encountered: