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
My team has rewritten some venom test scenarios with 2 levels of custom-executor ( a test scenario calls a custom-executor having the route, assertions...per step, this executor calls a second custom-executor having less specific data such as headers, certificates, high-level assertions) in order to :
have unified generic approach
avoid repeating code
lighten scenarios implementation
I recently joined the team and I've been told that implementation we adopted about mid last year have slowed down the scenarios execution from about 12m (503 tests scenarios) previously to about 45m (593 tests scenarios)
Feel free to reach me out to get the pipelines links
Is there anything we can do to get back the previous pace of execution ? (those are mostly REST call, they shouldn't take more than tens of seconds each)
Hi,
My team has rewritten some venom test scenarios with 2 levels of
custom-executor
( a test scenario calls a custom-executor having the route, assertions...per step, this executor calls a second custom-executor having less specific data such as headers, certificates, high-level assertions) in order to :I recently joined the team and I've been told that implementation we adopted about mid last year have slowed down the scenarios execution from about 12m (503 tests scenarios) previously to about 45m (593 tests scenarios)
Feel free to reach me out to get the pipelines links
Is there anything we can do to get back the previous pace of execution ? (those are mostly REST call, they shouldn't take more than tens of seconds each)
Thanks!
cc @gbahezre
The text was updated successfully, but these errors were encountered: