Dear colleagues,
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 LoadC...
Tom_S :
Hi,
Not sure this is a solution. Adding new steps still leaves us with more than one identical copy of the initial sequence (e.g. login procedure) and thus maintenance problem is not eliminated.
For example: assume there are 'Login>Logout" and "Login>BrowseHomePage>Logout" sequences (aka load tests). Now something changed in, say, Login process. What can be suggested except re-recording of both existing sequences to reflect changes in Login and make both tests to be again up-to-date?