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 User defined executors ( a test scenario calls a user defined executor having the route, assertions...per step, this executor calls a second user defined 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've done a simple benchmark locally : simple http calls vs 2 levels of user defined executors with 4 calls each. It seems like time of parsing for the executors layers increases time by 6* (see screenshot below)
As we have hundreds of API tests relying on venom executed frequently, the time of execution for those significantly increased (about times 7).
Is there anything we can do to improve the time of execution ? (those are mostly REST call, they shouldn't take more than tens of seconds each)
The text was updated successfully, but these errors were encountered:
BenHaramboure
changed the title
Custom executor - Several levels slow down test execution
User defined executor - Several levels slow down test execution
Feb 27, 2025
Hi,
My team has rewritten some venom test scenarios with 2 levels of
User defined executors
( a test scenario calls auser defined executor
having the route, assertions...per step, this executor calls a seconduser defined executor
having less specific data such as headers, certificates, high-level assertions) in order to :I've done a simple benchmark locally :
simple http calls
vs2 levels of user defined executors
with 4 calls each. It seems like time of parsing for the executors layers increases time by 6* (see screenshot below)As we have hundreds of API tests relying on venom executed frequently, the time of execution for those significantly increased (about times 7).
Is there anything we can do to improve the time 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: