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...
Hi Tom_S
I gave it a try yesterday using the Save As feature to try and make it work but unfortunately as it currently is the best you could do is create the starting point test to copy and then record anything after that, even if its a duplicate piece. Correct me if I'm wrong and couldn't find it but the Save As can only create a new test and not copy a piece to an existing one.
Other thing I hit is that it looks like all tests must start with a page navigation event which means you aren't able to create purely partial test pieces that only contain mouse, keyboard, etc events that depend on a previous piece doing the initial navigation.
Hi MPunsky
That's exactly right yes, to give an example from what I am migrating across from Visual Studio to LoadNinja.
The way I designed our test structure there is a folder of tests called "Components", each one of these is responsible for the actual page interactions and only contain a part of a full test, e.g. Login, Open Account, Secure Messages, etc. each item encapsulation to itself and its purpose to be chained together for use.
I then have a "User Journey" folder of tests which only ever call Components and never the page directly, these ones are responsible for orchestrating the whole journey under test and managing the top level items like the input data, output logging, etc.
To match that up to what you said, the Components would be the Modules and the User Journeys would be the Test Script that references the Modules