I am pretty sure that compaund Web Test is in your plans for the next LoadNinja update.
The purpose of compaund Web Test is similair to the Call Scenario operation from LoadComplete and its purpose to make it possible to create reusable parts of Web Test.
For example, assume that I need to load test a scenario when 80% of VUs just browse some goods catalogue and only 20% of all VUs do a purchase.
Current implementation of LoadNinja requires that the browse sequence must be recorded (and supported) twice - for browse test and for browse and purchase one.
Compaund Web Test should eliminate this duplication.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.